StatusHelpChangeForge
Help Center

Real Data

Common Error Codes

Last updated 13 days ago

HTTP status codes

  • 400 Bad Request: Invalid input data. Check that the request body matches the expected format.
  • 401 Unauthorized: Missing or invalid authentication. Include a valid API key or be logged in.
  • 403 Forbidden: You don't have permission. Possible causes: wrong role, product turned off, or an action that needs a Pro plan, such as creating an API key.
  • 404 Not Found: The resource doesn't exist or belongs to a different account.
  • 409 Conflict: Duplicate resource or a concurrent operation in progress (for example, an open checkout session).
  • 429 Too Many Requests: Rate limit exceeded. Wait for the number of seconds in the Retry-After header, or 1 minute if there is none, then retry.
  • 500 Internal Server Error: Something went wrong on our end. If this persists, contact support.
  • 503 Service Unavailable: A temporary problem on our end. Wait a few seconds and retry.

MCP-specific errors

  • Missing or invalid API key: The Authorization header is missing or doesn't start with Bearer sf_.
  • Invalid API key: No key matches. Check that it wasn't revoked.
  • Service temporarily unavailable, please retry shortly: The server couldn't check your key in time. Retry after 5 seconds. Your key is fine.
  • Parse error: The request body isn't valid JSON.
  • Unknown tool: <name>: That tool doesn't exist. Check the tool name spelling.
  • Method not found: <method>: The server doesn't support that JSON-RPC method.
  • Tool returns isError: true: The request reached the server, but the tool failed, usually because the API call it made returned an error. The error text explains why.
Was this helpful?

Related Articles

Can't find what you're looking for?

Contact Support