API

Error codes

Every error has the same envelope: a stable code, a message, a fix that says what to change, a retryable flag, a docs link and a request id. Match on the code, not the message. Retryable says whether sending the same request again can work. Quote the request id when you write to us.

Updated 2026-10-26

The envelope

The body is {"error":{"code","message","fix","docs_url","retryable","request_id"}}. The code is safe to match on; the message and fix are for people.

Codes

CodeUsual statusWhat it means
unauthorized401The API key is missing, malformed, revoked or unknown.
forbidden403This API key is not allowed to make this request.
insufficient_creditsvariesReturned when the request breaks this rule; the message and fix fields say what to change.
rate_limited429Too many requests for this API key.
invalid_input400The request input is invalid.
unknown_productvariesReturned when the request breaks this rule; the message and fix fields say what to change.
method_not_allowedvariesReturned when the request breaks this rule; the message and fix fields say what to change.
payload_too_largevariesReturned when the request breaks this rule; the message and fix fields say what to change.
provider_unavailable503The data source for this product is unavailable right now.
internal_error500An unexpected error occurred.
not_found404Nothing exists at this address.
conflict409The request conflicts with the current state of the resource.
signature_invalid400The request signature is missing or does not match.
plan_limit402The current plan does not allow this.
subscription_required402This needs an active subscription.
trial_expiredvariesReturned when the request breaks this rule; the message and fix fields say what to change.
account_limit402The plan allows no more connected accounts.
queue_limit402The plan allows no more queued scheduled posts.
allowance_used402A monthly allowance of the plan is used up.
media_storage_full503Media storage is full for now.
daily_cap409The account reached its daily posting limit for that day.
horizon400The time is further ahead than the plan schedules.
invalid_for_platform422The post breaks a rule of the destination.
reconnect_needed409The account must be connected again before it can post.
no_free_slot409There is no free weekly slot for these accounts.
media_not_readyvariesReturned when the request breaks this rule; the message and fix fields say what to change.
outcome_unknown409The destination may already have the post, so it is not retried.
feature_offvariesReturned when the request breaks this rule; the message and fix fields say what to change.
Try it

Start a trial

7-day trial for $1. Connect your accounts and schedule a week of posts in one sitting.

Start a trial
Free in your browser

Free tools

Count characters the way each network does, split threads and preview posts. No account needed.

Open the tools
For builders

API and MCP

Post to every network from your own code or assistant with one key, signed webhooks and idempotent requests.

See the API

Questions

Which errors should I retry?

Those with retryable true, such as rate_limited and internal_error, after the wait in Retry-After. Fix the others first.

From one post to every feed

Plan the week in one sitting, keep your team in the loop, and let 1Post publish on time while you get on with the rest of your day.