For the complete documentation index, see llms.txt. This page is also available as Markdown.

Connection and endpoint index

Choose MCP or REST, verify authentication with a read-only request, and find the supported operations.

Compact reference for agents making REST requests. All endpoint paths below are relative to https://backend.blotato.com/v2. For task instructions, read the workflow guide. For tool calls, use the MCP reference.

Connection

Reuse an authorized connection when available. Verify with blotato_get_user or REST GET /v2/users/me, then list accounts before selecting a publishing destination. Authentication success is not publication readiness. Keep API keys in credential storage, not in chat or committed files. Follow authentication and trial requirements before creating a key.

BLOTATO API REFERENCE
=====================

IMPORTANT: CHECK HOW YOU ARE CONNECTED
- If you have blotato_create_post, blotato_list_accounts, etc. as MCP tools:
  You are connected via MCP. Call those tools directly. You do NOT need HTTP
  endpoints, base URLs, or auth headers. See tool descriptions for parameters.
- If you are making HTTP requests directly (no MCP tools available):
  Use the REST API reference below.

REST API:
Base URL: https://backend.blotato.com/v2
Auth Header: blotato-api-key: YOUR_API_KEY
Content-Type: application/json

API KEY FORMAT: Your key sometimes ends with one or more "=" characters (base64
padding). The "=" is part of the key. Send it exactly. Do not strip, trim, or
URL-encode it. In shells, .env files, and scripts, wrap the key in single quotes
(for example 'abc123=='), to preserve the value.
For a 401, verify the complete key and authentication method. Verify with GET /users/me.

Posts, sources, visuals, comments, and messages use asynchronous completion.
Use each operation's status rules. Presigned upload is a separate request/PUT/URL flow.

Continue with the REST quickstart, OpenAPI reference, or error reference.

Mcp tool β†’ rest api mapping (for reference only)

This table maps operations, not interchangeable payloads. MCP uses tool arguments and transforms some responses. REST uses its own request wrappers and response shapes. Read REST versus MCP before translating a call.

Rest api endpoints

For metric names and availability, use Analytics metrics. For ID selection and optional playlists, use Accounts and identifiers.

Return to the agent reference index.

Last updated