Error handling

Copy

• Copy for LLM

  Copy page as Markdown for LLMs
• View as Markdown

  Open this page as Markdown
• Open in ChatGPT

  Get insights from ChatGPT
• Open in Claude

  Get insights from Claude
• Connect to Cursor

  Install MCP server on Cursor
• Connect to VS Code

  Install MCP server on VS Code

Spotnana uses the following standard HTTP response codes to indicate the status of an API request:

• 2xx Successful – The request was successfully received, understood, and accepted.
• 4xx Client error – The request contains bad syntax or invalid parameter.
• 5xx Server error – The server failed to fulfil a request.

Sample error message

Apart from the standard HTTP error codes, the error response contains a errorMessages > errorCode field that gives you additional context about the error.

Here are some sample API error responses:

Sample 1: HTTP/1.1 400 Bad Request

{
    "debugIdentifier": "https://debug.services.spotnana.com/file-search-results/5404d15aa99f5e2d4?q=debugid",
    "errorMessages": [
        {
            "errorCode": "INVALID_EMAIL_DOMAIN"
        }
    ]
}

Sample 2: HTTP/1.1 401 Unauthenticated

{
  "debugIdentifier": "https://debug.services.spotnana.com/file-search-results/null_a1fc321663723ce3?q=debugid",
  "errorMessages": [
    {
      "errorCode": "USER_NOT_AUTHENTICATED"
    }
  ]
}

Known error codes

429 - Rate limit exceeded

When generating an authentication token if you encounter the 429 Rate limit exceeded status with the following error:

{
      "errorCode": "TOO_MANY_REQUESTS"
}

It indicates that the rate limit for the auth endpoint has been exceeded.

Note: API calls to the /v2/auth/oauth2-token and /get-auth-token endpoints are rate limited. We recommend reusing the existing tokens in subsequent API calls until they expire.