Skip to main content
Suki uses standard HTTP status codes to indicate the outcome of an API request.
  • 2xx codes indicate success.
  • 4xx codes indicate a client-side error (e.g., you omitted a required parameter or provided an invalid configuration).
  • 5xx codes indicate a server-side error on Suki’s end. These are rare.
The following table lists the most common HTTP status codes you may receive.
CodeTitleDescription
200OKThe request was successful.
201CreatedThe resource was created successfully. The URL for the new resource is in the Location header.
204No ContentThe request was successful, and there is no content to return.
400Bad RequestThe request was unacceptable, often due to malformed syntax or a missing parameter.
401UnauthorizedThe request was not authenticated. This could be due to missing, invalid, or insufficient credentials.
402Over QuotaThe request was valid, but you have exceeded your plan’s quota or rate limits.
404Not FoundThe requested resource does not exist.
409ConflictThe request conflicts with the current state of the resource (e.g., the resource already exists, or the request was based on stale data).
422Validation FailedThe request was parsed correctly but failed a validation rule.
429Too Many RequestsYou have sent too many requests in a short period. We recommend using an exponential backoff strategy for your requests.
500, 502, 503, 504Server ErrorsAn unexpected error occurred on Suki’s servers.
⌘I