This legacy information is part of v1, v2, or v3, which will be supported only until March 31, 2027. To avoid disruption, migrate your integration to v4 before that date. For endpoint mappings, Bearer token authentication, and scoped API key guidance, see the Migrating to v4 article in the Developer's Guide.
Voiso
uses standard HTTP response codes to convey the outcome of an API request precisely:
- 2xx codes indicate successful execution.
- 4xx codes indicate errors resulting from incomplete or incorrect input information.
- 3xx codes indicate redirection. The requested resource is accessible elsewhere on the server.
- 5xx codes indicate errors originating from issues on the Voiso server side.
Tip: Consult the endpoint documentation for a more granular understanding of HTTP response codes.
| Code | Text | Description |
|---|---|---|
| 200 | OK | The request is successfully completed. |
| 201 | Created | The requested resource is successfully created. |
| 204 | No Content | The request is successfully completed, and there is no content in response. |
| 301 | Moved Permanently | The requested resource is moved successfully. |
| 400 | Bad request | The request could not be completed due to a client-related error. |
| 401 | Unauthorised | The request is unsuccessful as it lacks valid authentication credentials for the resource. |
| 403 | Access forbidden | The user does not have the required permissions assigned to their role. |
| 404 | Not Found | The requested resource or endpoint is not found. |
| 405 | Method Not Allowed | The requested resource is found, but it does not support the HTTP method used. |