REST API quickstart

Configure REST authentication, connect social accounts, and verify access before publishing or building an automation.

Use this path for HTTP requests, n8n, or Make. To give instructions to Claude, Codex, or another assistant, start with MCP setup.

Your first verified result is an account-list response. Publishing comes after account selection and platform checks.

Get Started with Blotato API

The Blotato API allows you to:

• publish and schedule posts directly to social media platforms

• supports text, image, videos, reels, slideshows, carousels, threads, and stories

• create images, videos, slideshows, and carousels programmatically via templates

It is limited to paying subscribers in order to reduce spam and service abuse, keeping Blotato's integration in good standing with the social platforms.

---

Plans That Include API

Plan	API Access
Free Trial	No
Starter	Yes
Creator	Yes
Agency	Yes

API access is included on every paid plan. Generating an API key from Settings > API immediately ends a free trial and activates your paid Starter subscription.

---

Base URLs

Blotato has two base URLs. Use the one that matches your integration:

Integration	Base URL
REST API (direct HTTP, n8n, Make)	https://backend.blotato.com/v2
MCP Server (ChatGPT, Claude Code, Claude Cowork, Claude Desktop, Cursor, Antigravity)	https://mcp.blotato.com/mcp

api.blotato.com is not a valid base URL. If your AI tool reports a DNS error for api.blotato.com, it guessed wrong. Use one of the two URLs above.

---

1. Get Your API Key

❗IMPORTANT: this will end your free trial immediately and start your paid subscription.

Go to Accounts > API > click "Generate API Key".

---

2. Connect Social Accounts

Go to Accounts and connect your social accounts. If you get stuck, more information here:

Social accounts | Blotato Helphelp.blotato.com

---

3. Verify access

Ask your agent or HTTP client to send this request with your API key:

GET /v2/users/me/accounts HTTP/1.1
Host: backend.blotato.com
blotato-api-key: YOUR_API_KEY

A successful response contains items. An empty items array confirms access but means no social accounts are connected. Use each account's returned id as accountId.

Next, follow Publish and verify a post, or choose another agent workflow. Use Accounts and identifiers for Page, board, and playlist IDs.

Optional: install the Blotato integration

n8n

1. Follow the Blotato node installation guide for n8n Cloud or self-hosted n8n.

2. Configure and verify the credential.

3. Use the first-post workflow after selecting the intended account.

Make

1. Open any scenario in Make

2. Click the "+" icon to add a module

3. Search for "Blotato"

4. Select the Blotato module

---

Choose an automation tutorial

New to building automations? Start here:

• Build Your First AI Automation - Build an n8n source-to-visual-to-post workflow with completion checks.

Choose your preferred integration path:

• MCP Server - control Blotato from ChatGPT, Claude.ai, Claude Desktop, Claude Code, Cursor, and more with natural language

• n8n - post everywhere

• Make - post everywhere

• REST API - OpenAPI reference and Examples Below

Blotato has official Make.com and n8n nodes. Zapier does not have an official Blotato app. In Zapier, use Webhooks by Zapier to send authenticated HTTP requests to the Blotato API.

Check out more workflow automation templates here:

https://help.blotato.com/api/templateshelp.blotato.com

---

Troubleshoot errors

Use the Logs and click on each request to see full payload, response, and error message:

Logs (for debugging): https://my.blotato.com/logs

FIX MY AUTOMATION (n8n only): On a failed n8n request in the Logs, click the green FIX MY AUTOMATION button and Blotato AI will attempt to fix your n8n workflow automatically. This feature is for n8n only -- it does not work for Make, Claude, MCP, or direct REST API calls. Full walkthrough: Fix My Automation.

---

Raw REST API Calls - Examples

Authentication

To authenticate API requests, include your Blotato API key in the request headers.

Authentication Header

blotato-api-key: YOUR_API_KEY

Requests without a valid API key will be rejected and 401 error will be returned.

Your API key sometimes ends with one or more = characters. Copy the full value, including these characters. Use the quoting required by your client or configuration format. For a 401, follow authentication checks.

Step 0: Get Your Account IDs

Before publishing, fetch your connected accounts to get the accountId:

GET https://backend.blotato.com/v2/users/me/accounts HTTP/1.1
blotato-api-key: YOUR_API_KEY

Use the id from the response as your accountId. For Facebook and LinkedIn, also fetch subaccounts to get pageId. See Accounts reference for details.

Post to a Platform Immediately

POST https://backend.blotato.com/v2/posts HTTP/1.1
Content-Type: application/json
blotato-api-key: YOUR_API_KEY

{
  "post": {
    "accountId": "98432",
    "content": {
      "text": "Hello, world!",
      "mediaUrls": [],
      "platform": "twitter"
    },
    "target": {
      "targetType": "twitter"
    }
  }
}

After submission, save postSubmissionId and poll GET /v2/posts/:postSubmissionId until published or failed. A 201 create response confirms acceptance. Follow the completion rules before reporting success.

Post at a Scheduled Time

POST https://backend.blotato.com/v2/posts HTTP/1.1
Content-Type: application/json
blotato-api-key: YOUR_API_KEY

{
  "post": {
    "accountId": "98432",
    "content": {
      "text": "Scheduled post example",
      "mediaUrls": [],
      "platform": "facebook"
    },
    "target": {
      "targetType": "facebook",
      "pageId": "987654321"
    }
  },
  "scheduledTime": "2030-06-15T15:00:00Z"
}

Replace the example date with the user's intended future time in UTC. To use the next available calendar slot, replace scheduledTime with useNextFreeSlot: true. Both are top-level fields, outside post. See Scheduling.

Post a Twitter Thread with Multiple Posts

POST https://backend.blotato.com/v2/posts HTTP/1.1
Content-Type: application/json
blotato-api-key: YOUR_API_KEY

{
  "post": {
    "accountId": "98432",
    "content": {
      "text": "This is the first tweet in the thread.",
      "mediaUrls": [],
      "platform": "twitter",
      "additionalPosts": [
        {
          "text": "Here's the second tweet, adding more info.",
          "mediaUrls": []
        },
        {
          "text": "And here's the third tweet to conclude!",
          "mediaUrls": []
        }
      ]
    },
    "target": {
      "targetType": "twitter"
    }
  }
}

Attach Media to Post (images and videos)

Pass any publicly accessible image/video URL into the mediaUrls parameter. No upload step required. Blotato handles the media transfer.

For local files without a public URL, use the Presigned Upload endpoint to upload directly to Blotato. No Google Drive or S3 needed.

POST https://backend.blotato.com/v2/posts HTTP/1.1
Content-Type: application/json
blotato-api-key: YOUR_API_KEY

{
  "post": {
    "accountId": "98432",
    "content": {
      "text": "Check out this image!",
      "mediaUrls": [
        "https://example.com/image.jpg"
      ],
      "platform": "instagram"
    },
    "target": {
      "targetType": "instagram"
    }
  }
}

The optional Upload Media endpoint is still available if you need to host media on Blotato's servers. See Upload Media.

---

For AI Agents

If you are an AI agent or LLM integration, start with the plain-text API reference:

API Reference for LLMs

This index links to references by task, including request examples, status values, and workflow instructions.

For async workflow patterns and code examples, see Protocol and Recipes.

For the full endpoint reference, see API Reference.