| Table of Contents |
|---|
HTTP responses
Even tough explicitly mentioned in each API description there is a set of basic HTTP responses that due to an error (either in your request or internally in DDS) can be returned to your application. It is imperativ that you handle these errors with care and take action according to the type of errors you receive. The HTTP response code is your first and best guide to understand what has happened.
...
| Code | Meaning | Action |
|---|---|---|
| 400 | Bad request. Usually means that your request was not sufficient for the API to handle your request. | Debug code, contact Bokbasen for assistance if needed. |
| 401 | Unauthorized. Something is wrong with your authentication header, most of the time either your TGT has expired or your are missing the bearer token (Bokbasen) before the TGT in the header. | Recreate TGT. If that does not help: Debug code, contact Bokbasen for assistance if needed. |
| 404 | Not found. Something is wrong with your URL and you requested a resource that does not exist. | Debug code, contact Bokbasen for assistance if needed. |
| 405 | Method not allowed. Check your request method, if you e.g. try to retrieve a resource using POST, this is the error you will get. | Debug code, contact Bokbasen for assistance if needed. |
| 500 | Internal server error. An unknown error occurred. | Contact Bokbasen following the reporting errors guidelines |
Reporting errors guidelines
Bokbasen is happy to support you in your efforts on integrating towards our APIs, but in order to give sufficient help we need enough information for us to be able to do that. When sending a request regarding problems with and API call, please always include:
...