The Daisycon Advertiser API uses standard HTTP status codes to indicate whether a request succeeded or failed. When a request fails, the response typically includes an error object with additional details about the problem.
For the full endpoint documentation and response models, see the Swagger documentation for the Advertiser API.
Common HTTP status codes
- 200 OK – The request was successful and returned data.
- 201 Created – A resource was successfully created.
- 204 No content – The request succeeded but no data is returned.
Client errors
- 400 Bad request – The request is invalid or contains incorrect parameters.
- 401 Unauthorized – The request does not include valid authentication.
- 403 Forbidden – The authenticated user does not have permission to access this resource.
- 404 Not found – The requested resource does not exist or cannot be accessed.
- 405 Method not allowed – The HTTP method is not supported for this endpoint.
- 409 Conflict – The request conflicts with the current state of the resource.
- 422 Unprocessable content – The request format is correct but the data cannot be processed.
- 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
- Check that your OAuth access token is valid and not expired.
- Verify that the advertiser ID and other resource IDs exist.
- Confirm that the authenticated user has permission to access the resource.
- Validate the request parameters and request body.
For endpoint specific response details and error models, consult the Advertiser API Swagger documentation.