To ensure a smooth integration, it is important to understand why a request might fail. Most API errors in the DISPL system occur during the transition from Draft to Active or during the File Upload phase.
API Error Reference Table
| Status Code | Common Reason | How to Fix |
|---|---|---|
| 401 Unauthorized | Missing or expired Bearer Token. | Re-run the /login/token/ request to get a fresh token. |
| 403 Forbidden | Incorrect x-adexchange-role header. | Ensure header is set to dsp. |
| 402 Payment Required | Agency balance is zero or negative. | Top up the agency account balance in the dashboard. |
| 404 Not Found | Wrong Agency ID or Request ID in the URL. | Double-check the ID in the dynamic portion of the URL. |
| 413 Payload Too Large | Video file exceeds the size limit. | Compress the video or check the network's maximum file size. |
| 422 Unprocessable Entity | Missing required fields (e.g., duration). | Verify all mandatory parameters from the JSON table are present. |
Visualizing the Troubleshooting Flow
If your campaign isn't playing, follow this logic to find the "blocker":
Final Pro-Tips for a Stable Integration
Idempotency: If a request fails due to a network timeout, check the list of campaigns before retrying to avoid creating duplicate "Test Campaigns."
Validation: Before uploading, use a tool like
ffprobeor a library in your code to verify the video's duration and resolution match exactly what you send in thePOSTparameters.Logs: Always log the
x-request-id(returned in the response headers). If you need to contact technical support, providing this ID allows them to find your specific request in the server logs instantly.
Comments
0 comments
Please sign in to leave a comment.