HTTP Status Codes

The Sinch Subproject API returns an HTTP status and code each time a request is made. Here, you will find more information on each status.

The following HTTP status codes are used by the API. Additional codes might be added in the future and if you encounter a code not in this list please consult the HTTP specification for a definition.

Status Reason Description
200 OK The request was successful.
400 Invalid Argument The request doesn't conform to the API.
401 Unauthenticated The authentication token is invalid. If the issue persists, try generating a new one in the Sinch Customer Dashboard.
403 Permission Denied The request syntax is valid but can't be performed. Unauthorized to act on specified project (either because the parent project doesn't exist or the client permission is missing).
404 Not Found The path is invalid or no resource exists with the given ID.
409 Already Exists The subproject already exists. Either create a new subproject or update the existing one.

Customers: Please contact your account manager for further assistance with error codes. Contact information can be found on the homepage of the Sinch Customer Dashboard.

Internal Employees: Please use the ent-eng-identity-access Slack channel for further assistance.

We'd love to hear from you!
Rate this content:
Still have a question?
 
Ask the community.