Skip to main content
Sigma uses conventional HTTP response codes to indicate whether a request succeeded or failed:
  • 2xx codes indicate the request was received and processed successfully
  • 4xx codes indicate a problem with the request — missing fields, invalid values, or authentication issues
  • 5xx codes indicate a server-side error on Sigma’s end
CodeMeaningWhat to do
200SuccessRequest was processed successfully. Read the response body for results.
400Bad RequestThe request is malformed or missing required fields. Check the error message in the response body and fix the request before retrying.
401UnauthorizedThe request is missing valid API credentials. Ensure your apiKey and apiSecret headers are included and correct.
404Not FoundThe requested resource does not exist. Check the endpoint URL and any IDs in the path.
429Too Many RequestsYou have exceeded the rate limit. Wait before sending further requests. Consider adding retry logic with exponential backoff in your integration.
500, 502Server ErrorAn unexpected error occurred on Sigma’s end. Contact support if the issue persists.

​
Error Response Format

When a request fails, the response body includes details about what went wrong: 
{
  "status": "error",
  "message": "Validation failed",
  "errors": [
    {
      "field": "amount",
      "message": "amount is required"
    }
  ]
}
Use the message and errors fields to identify and fix the issue before retrying.