The Daisycon Publisher API uses standard HTTP status codes to indicate whether a request succeeded or failed. When an error occurs, the API response usually includes additional information describing the problem.
Detailed response models and endpoint behaviour can be found in the Publisher API Swagger documentation.
Common HTTP status codes
- 200 OK – The request was successful and returned data.
- 201 Created – A new resource was created successfully.
- 204 No content – The request succeeded but no response body is returned.
Client errors
- 400 Bad request – The request contains invalid parameters or missing data.
- 401 Unauthorized – Authentication failed or is missing.
- 403 Forbidden – The authenticated user does not have permission for this action.
- 404 Not found – The requested resource does not exist.
- 405 Method not allowed – The HTTP method is not supported for the endpoint.
- 409 Conflict – The request conflicts with the current resource state.
- 422 Unprocessable content – The API understands the request but cannot process the provided data.
- 429 Too many requests – The API rate limit has been exceeded. Reduce the number of requests or wait before sending new requests. See the Daisycon API rate limits documentation for details.
Server errors
- 500 Internal server error – An unexpected error occurred on the server.
- 503 Service unavailable – The API service is temporarily unavailable.
Troubleshooting
- Verify that your OAuth access token is valid.
- Check that the publisher ID and related resource IDs are correct.
- Confirm the authenticated user has permission to access the requested data.
- Review the request parameters and payload.
For endpoint specific responses and error objects, consult the Publisher API Swagger documentation.