Access and authentication
Distinguish paid access, API-key authentication, OAuth authorization, and client-specific connection failures.
API and MCP access is included in paid Starter, Creator, and Agency subscriptions. The free trial does not include API or MCP access. Generating an API key during a trial ends the trial and starts the paid subscription.
REST API
Open Settings > API.
Generate or copy your API key.
Include the key in the
blotato-api-keyheader of each request.Call
GET https://backend.blotato.com/v2/users/me/accountsto verify access.
GET /v2/users/me/accounts HTTP/1.1
Host: backend.blotato.com
blotato-api-key: YOUR_API_KEYCopy the full key, including any trailing = characters. Preserve the value exactly. JSON values use double quotes. Store credentials in your client's secret settings or environment, outside published examples.
MCP
The server uses Streamable HTTP at https://mcp.blotato.com/mcp and accepts these authentication methods:
OAuth
Add the server URL and complete the browser authorization flow
API key header
Set blotato-api-key to your API key
Bearer header
Set Authorization to Bearer YOUR_API_KEY
Use the configuration supported by your client in the setup guide. A field named “Bearer token env var” expects an environment variable name, rather than the key itself. For a header-value form, paste the key into the header value.
After connecting, ask the assistant to call blotato_list_accounts. An empty array is a successful authenticated response with no connected accounts.
Resolve access errors
401 or invalid credentials
Recopy the full API key, or repeat OAuth authorization in the client
403 with a subscription message
Check the subscription in Billing
OAuth fails but an API-key request succeeds
Follow the OAuth session troubleshooting steps for the client
Accounts are missing
Confirm the Blotato account used to authorize, then check Social accounts
Use the returned error to choose the next step. An OAuth error alone does not establish a billing problem.
Last updated