How To Create Blog Posts

This article demonstrates how to create and immediately publish blog posts using Wix Blog REST API, including handling external images, rich content formatting, and proper media management workflow.

Part 0: Get an Author/Member ID (Required for 3rd-Party Apps)

IMPORTANT: When calling the Blog API as a 3rd-party app (not as the site owner), draftPost.memberId is required. The API will reject requests with “Missing post owner information” if omitted.

A memberId is the id of a site member (Wix Members). Only the Members API produces one. Run the two steps below in order and stop as soon as you have an id — do not go looking for an author id anywhere else (see What is not a memberId).

1. Query site members using List Members (opens in a new tab):

   bashCopy

   curl -X GET "https://www.wixapis.com/members/v1/members?fieldsets=PUBLIC&paging.limit=1" \
     -H "Authorization: <AUTH>"

   If the response contains a member, use members[0].id as draftPost.memberId and skip step 2. That member becomes the post author.

2. If the site has no members yet — the response is {"members": [], "metadata": {"count": 0, "total": 0, ...}} — create the author member yourself with Create Member (opens in a new tab). This is the normal case on a new site or a site that only has Blog installed: nobody has signed up, so there is no member to reuse. Creating the author is a prerequisite of the post the user asked for, not a separate decision — create it, then say so in your summary.

   bashCopy

   curl -X POST "https://www.wixapis.com/members/v1/members" \
     -H "Authorization: <AUTH>" \
     -H "Content-Type: application/json" \
     -d '{
       "member": {
         "loginEmail": "blogauthor@example.com",
         "contact": { "firstName": "Blog", "lastName": "Author" }
       }
     }'

   Use member.id from the response as draftPost.memberId. The new member comes back with status: "APPROVED", and its profile.nickname is derived from the contact name. That nickname is the author name the blog displays, so pass the name the user wants shown (or set member.profile.nickname explicitly). If the user named an author, use their name; otherwise a generic author like the example above is fine.

What is not a memberId

These are the wrong places to look, and probing them costs a round trip each:

• Site collaborators / contributors are Wix users, not site members. The Contributors API (opens in a new tab) returns account and user ids, which the Blog API will not accept as a memberId.
• A contact is not a member. Querying Contacts (opens in a new tab) returns contact ids; only members have a memberId. On a site with no members the contacts query is usually empty too.
• GET https://www.wixapis.com/identity/v1/users returns 404. There is no site-scoped identity endpoint to read the site owner from. Do not try it.

Part 1: Import External Images to Wix Media Manager

1. Identify external image URLs from user input for cover images and embedded content images.

2. Import each external image using Import File (opens in a new tab). This converts external URLs to Wix Media IDs required for blog posts.

   bashCopy

   curl -X POST "https://www.wixapis.com/site-media/v1/files/import" \
     -H "Authorization: <AUTH>" \
     -H "Content-Type: application/json" \
     -d '{
       "url": "https://example.com/image.jpg",
       "mediaType": "IMAGE",
       "displayName": "Cover Image.jpg"
     }'

   The response will include a file.id field. Use this ID in blog post creation. Images with operationStatus: "PENDING" can be used immediately.

3. Store the returned file IDs for use in blog post creation.

Part 2: Create Blog Post with Rich Content

You have two endpoints:

• Single post: Create Draft Post (opens in a new tab) — POST https://www.wixapis.com/blog/v3/draft-posts
• Multiple posts (preferred for any N ≥ 2): Bulk Create Draft Posts (opens in a new tab) — POST https://www.wixapis.com/blog/v3/bulk/draft-posts/create

Use the bulk endpoint when seeding multiple posts — one call replaces N single-post calls and avoids the per-call latency of ~25–30 s each.

Single-post endpoint

Bulk-create endpoint (preferred for multiple posts)

⚠️ Body shape — read this carefully. Each item in draftPosts is a FLAT post object: {title, memberId, richContent, media?, ...}. Do NOT wrap each item in a draftPost field. Unlike the single-post endpoint (which uses {draftPost: {...}} because the request is one post), the bulk endpoint puts each post DIRECTLY inside the draftPosts array.

✅ CORRECT body shape (verified against the live API — returns 200 with results[].itemMetadata.success: true):

❌ WRONG body shape (returns 400 Bad Request with draftPosts[i].title must not be empty because the API is looking for draftPosts[i].title directly and finds it nested under a draftPost field):

The natural intuition is “the bulk endpoint reuses the single-post {draftPost: {...}} envelope, just inside an array” — that’s wrong. The bulk endpoint flattens the envelope away because the array IS the envelope. Use the FLAT shape: draftPosts[i] IS the post.

Full bulk-create curl example

The response body is {results: [{itemMetadata: {id, originalIndex, success}}, ...]}. Each result’s itemMetadata carries the created post id and a success: boolean flag — the bulk call returns 200 even if some posts fail; check each results[i].itemMetadata.success individually.

Common URL-shape mistakes (do not use these — both return 404):

• /blog/v3/draft-posts/bulk ✗
• /blog/v3/draft-posts/bulk-create ✗
• The correct path is /blog/v3/bulk/draft-posts/create (note: bulk is a path segment between v3 and draft-posts, not a suffix on draft-posts).

2. Structure rich content using Ricos JSON format. Reference Ricos documentation (opens in a new tab) for complete node structure. Common node types:

   • PARAGRAPH for text content
   • HEADING for section headers
   • IMAGE for embedded images (requires Wix Media ID)
   • ORDERED_LIST and BULLETED_LIST for lists
   • BLOCKQUOTE for quoted text
   • LIST_ITEM for individual list items

   CRITICAL: All TEXT nodes MUST be wrapped in PARAGRAPH nodes within their parent containers.

   Correct Ricos structure example:

   jsonCopy

   {
     "nodes": [
       {
         "type": "PARAGRAPH",
         "nodes": [
           {
             "type": "TEXT",
             "textData": {
               "text": "This is a paragraph with some content.",
               "decorations": []
             }
           }
         ],
         "paragraphData": {}
       }
     ]
   }

   Correct BLOCKQUOTE structure:

   jsonCopy

   {
     "type": "BLOCKQUOTE",
     "nodes": [
       {
         "type": "PARAGRAPH",
         "nodes": [
           {
             "type": "TEXT",
             "textData": { "text": "Quote text here", "decorations": [] }
           }
         ],
         "paragraphData": {}
   
   
   
   

   Correct LIST_ITEM structure:

   jsonCopy

   {
     "type": "LIST_ITEM",
     "nodes": [
       {
         "type": "PARAGRAPH",
         "nodes": [
           {
             "type": "TEXT",
             "textData": { "text": "List item text", "decorations": [] }
           }
         ],
         "paragraphData": {}
   
   
   

3. For embedded images in rich content, use IMAGE nodes with Wix Media IDs:

   jsonCopy

   {
     "type": "IMAGE",
     "nodes": [],
     "imageData": {
       "containerData": {
         "width": { "size": "CONTENT" },
         "alignment": "CENTER"
       },
       "image": {
         "src": { "id": "mediaId" },
         "width": 
   
   
   
   
   

4. Set publish: true to immediately publish the post rather than saving as draft.

Part 3: Handle Categories and Tags (Optional)

1. Resolve category IDs using List Categories (opens in a new tab) if user provides category names.

2. Resolve tag IDs using Query Tags (opens in a new tab) if user provides tag labels.

3. Include resolved IDs in categoryIds and tagIds arrays in the draft post object.

IMPORTANT NOTES:

• Never mock blog posts or media IDs - always use the APIs to import images and create posts
• Always read the full documentation of methods before implementation
• External images MUST be imported via Import File API before use in blog posts - direct external URLs will not work
• For 3rd-party app integrations, memberId is mandatory - get it from List Members (opens in a new tab), and if the site has no members yet, create one with Create Member (opens in a new tab) (see Part 0). Never substitute a contact id, a collaborator/contributor id, or a Wix user id for a memberId
• Use ONLY the file ID (without wix:image://v1/ prefix) for both cover images and embedded images
• Rich content IMAGE nodes require both width and height properties in the image object
• Images with "operationStatus": "PENDING" from import can be used immediately in blog posts
• Set publish: true in the request to publish immediately rather than save as draft
• For multiple posts, use Bulk Create Draft Posts API with draftPosts array
• Include fieldsets: ['URL'] to get post URLs in the response
• Handle image import failures gracefully - continue without images if import fails
• Provide meaningful displayName values during image import for better organization
• Use appropriate Ricos node types (PARAGRAPH, HEADING, LIST, etc.) for semantic content structure
• Consider batching image imports when creating multiple posts with many images

CRITICAL RICOS JSON STRUCTURE RULES:

• NEVER place TEXT nodes directly in BLOCKQUOTE, LIST_ITEM, or other container nodes
• ALL TEXT nodes MUST be wrapped in PARAGRAPH nodes within their parent containers
• BLOCKQUOTE nodes must contain PARAGRAPH nodes, which contain TEXT nodes
• LIST_ITEM nodes must contain PARAGRAPH nodes, which contain TEXT nodes
• Failure to follow proper nesting will result in parsing errors: “Expected a paragraph node but found TEXT”
• Always validate Ricos structure before sending to ensure TEXT nodes are properly nested

Troubleshooting