WEIR

Free tool

X API Error Decoder

Paste an error from the X (Twitter) API, a client library or Weir's API, and see what it means and what to do next. It reads HTTP statuses, v2 problem types such as client-not-enrolled and usage-capped, and v1.1 codes such as 88, 89, 187, 226 and 453.

  1. HTTP status

    429 Too Many Requests

    What it means: A rate limit or a usage cap was hit: too many calls in the current window, or the app's monthly allowance is used up.

    What to do: Wait until the time in the x-rate-limit-reset header (Unix seconds), then retry with backoff. If the body says usage-capped, the monthly cap is spent and waiting a few minutes will not help.

Every error in the table (47)
  • 400 Bad Request: The request itself is wrong: a parameter is missing or invalid, a field name is misspelled, or the search query does not parse.
  • 401 Unauthorized: No valid credentials reached X: the token is missing, malformed, revoked, or for another app.
  • 403 Forbidden: X knows who you are but will not let this credential do this: the app is not in a Project, the endpoint needs user-context auth or a higher access level, or the account is restricted.
  • 404 Not Found: The endpoint path is wrong, or the post or account does not exist, was deleted, or is not visible to this credential.
  • 429 Too Many Requests: A rate limit or a usage cap was hit: too many calls in the current window, or the app's monthly allowance is used up.
  • 500 Internal Server Error: Something failed on X's side.
  • 502 Bad Gateway: X's front servers could not reach the service behind them.
  • 503 Service Unavailable: X is overloaded or down for that endpoint.
  • 504 Gateway Timeout: X did not answer in time. Large searches and slow endpoints hit this first.
  • client-forbidden: client-not-enrolled: The app making the call is not attached to a Project, which v2 endpoints require.
  • unsupported-authentication: The endpoint needs a different kind of auth: usually OAuth 2.0 user context or OAuth 1.0a, not an app-only bearer token.
  • usage-capped: The app's monthly post-read cap or usage allowance is used up.
  • invalid-request: One or more parameters are invalid.
  • resource-not-found: An id you asked for has no post or account behind it. In a batch lookup this comes inside a 200 response, beside the ids that worked.
  • not-authorized-for-resource: The post or account exists but this credential may not see it, usually because the account is protected.
  • resource-unavailable: The account or post is unavailable, most often because the account is suspended.
  • disallowed-resource: The request touches a resource your app may not access.
  • Filtered stream rule errors: Adding stream rules failed: too many rules for your level, a rule that already exists, or a rule with an operator your level cannot use.
  • Stream connection errors: The filtered stream refused or dropped the connection: too many open connections, an operational reset, or a client too slow to keep up.
  • Code 32: Could not authenticate you: The OAuth signature or credentials were rejected.
  • Code 34: Sorry, that page does not exist: The endpoint or the resource does not exist.
  • Code 50: User not found: No account has that id or handle.
  • Code 63: User has been suspended: The account you asked about is suspended.
  • Code 64: Your account is suspended: The account behind the credentials is suspended.
  • Code 88: Rate limit exceeded: Too many requests to this endpoint in the current 15-minute window.
  • Code 89: Invalid or expired token: The access token was revoked or has expired.
  • Code 130: Over capacity: X is temporarily overloaded.
  • Code 131: Internal error: An unknown error on X's side.
  • Code 135: Timestamp out of bounds: The OAuth timestamp is too far from X's clock.
  • Code 144: No status found with that ID: The post was deleted or never existed.
  • Code 179: Not authorized to see this status: The post belongs to a protected account.
  • Code 185: Over daily status update limit: The account has posted as much as X allows for now.
  • Code 186: Tweet needs to be a bit shorter: The text is over the character limit for this account.
  • Code 187: Status is a duplicate: The same text was just posted.
  • Code 215: Bad authentication data: The request carried no usable authentication.
  • Code 220: Your credentials do not allow access to this resource: The token lacks the permission or scope this call needs.
  • Code 226: This request looks like it might be automated: X's spam defences blocked a write, often a burst of similar posts, follows or likes.
  • Code 261: Application cannot perform write actions: The app has been restricted to read-only.
  • Code 326: Account temporarily locked: X locked the account for suspicious activity.
  • Code 327: You have already retweeted this Tweet: The repost already exists.
  • Code 349: You cannot send messages to this user: The recipient does not accept direct messages from this account.
  • Code 385: Reply to a deleted or invisible post: The post being replied to is gone or not visible to this account.
  • Code 453: You currently have access to a subset of endpoints: Your access level does not include this endpoint, usually a v1.1 endpoint on a newer plan.
  • Weir: rate_limit_exceeded (429): Your key's per-minute limit, or a free monitor's hourly manual run, is used up.
  • Weir: quota_exceeded (402): The account has no credits left for this call.
  • Weir: source_unavailable (503): X or Reddit did not answer Weir in time, or the source is busy.
  • Weir: insufficient_scope (403): The API key lacks the scope this endpoint needs, such as read:x.

How it works

The decoder reads what you paste and matches the HTTP status, the v2 problem type, any v1.1 error code and Weir's own API errors against a built-in list, then says what the error means, the usual fix, and whether retrying will help.

It runs in your browser: nothing is sent, you don't need to sign in, and it uses no credits. It can't see your account, so for usage caps and billing errors check your developer console too.

Retry or fix

As a rule, a 429 or a 503 is worth retrying after a wait, while a 401, 402 or 403 comes back the same until you change something. Our guides to X API error codes, 402 Payment Required, rate limit errors, Tweepy 403 Forbidden and X API rate limits go deeper, and X API status helps when the problem is on X's side.

Questions

What does error 429 mean in the Twitter API?

Too Many Requests: you hit the rate limit for that endpoint or a usage cap on your plan. Wait until the time in the Retry-After or x-rate-limit-reset header (Unix seconds), then slow down; a usage cap only clears when it resets.

What does 403 Forbidden “client-not-enrolled” mean?

Your keys work, but the app behind them isn't enrolled for that endpoint, usually because it isn't attached to a Project or the plan doesn't include it. Retrying won't help; fix the app's setup or plan.

What is X API error 453?

A legacy access error that starts “You currently have access to a subset of X API V2 endpoints”. It appears when you call an endpoint, often a v1.1 one, that your access doesn't include; use the v2 endpoint or a plan that has it.

What does 402 Payment Required mean on the X API?

On X's pay-per-use plan, the request couldn't be paid for, usually because the account's credits ran out. Retries keep failing until credits are added.

What do v1.1 error codes 88, 89, 187 and 226 mean?

88 means the rate limit was exceeded, 89 an invalid or expired token, 187 a duplicate post, and 226 a request X judged to look automated. Paste the whole error here to see the fix for each.

What's the difference between 401 and 403?

401 Unauthorized means the credentials are missing, wrong or expired. 403 Forbidden means they are valid but not allowed to make that request.

Is anything I paste sent anywhere?

No. The decoder runs in your browser and sends nothing, so you can paste a full response. Still remove keys and tokens before you share an error anywhere else.