HTTP response codes
The Vipps APIs return the following HTTP statuses in the responses:
| HTTP status | Description |
|---|---|
200 OK | Request successful |
201 Created | Request successful, resource created |
204 No Content | Request successful, but empty result |
400 Bad Request | Invalid request, see the error for details |
401 Unauthorized | Invalid credentials |
403 Forbidden | Authentication ok, but credentials lacks authorization |
404 Not Found | The resource was not found |
409 Conflict | Unsuccessful due to conflicting resource |
429 Too Many Requests | Look at table below to view current rate limits |
500 Server Error | An internal Vipps problem. |
HTTP responses with errors from the application gateway contain one or more error JSON object.
Error responses from the application gateway include 401, 403, 422 and 429.
Note that the HTTP responses that contain errors from the Vipps backend will contain an array of JSON objects.
See the API specification for each API for details especially the FAQ.
In general:
- 2XX responses: Everything is OK.
- 4XX responses: Client error. You have a problem, and you must correct it.
- 5XX responses: Server error. We have a problem, and we must correct it.
The overview here is quite good: HTTP Status Codes Glossary.
The authoritative reference is: RFC 9110: HTTP Semantics.