Debugging HTTP & API Reference

Error Codes & Troubleshooting

Comprehensive guide to error codes, HTTP status responses, rate limits, and postback debugging tools.

1. Standard HTTP Status Responses

Code	Status	Meaning & Troubleshooting Action
200 OK	Success	Request succeeded. Your server should also respond with HTTP `200 OK` to acknowledge postbacks.
400 Bad Request	Validation Error	Missing required query parameters such as `apiKey` or `userId`. Check query string syntax.
401 Unauthorized	Invalid API Key	The provided `apiKey` does not exist or has been revoked. Verify in your Publisher App Settings.
403 Forbidden	Access Denied	The application is pending review, suspended, or the user is connecting through a detected VPN/proxy.
404 Not Found	Resource Not Found	Offer ID or Placement does not exist.
429 Too Many Requests	Rate Limited	API request threshold exceeded (default: 60 requests/minute per IP). Implement client-side caching.
500 Server Error	Internal Error	Unexpected platform error. Check network logs or reach out to support.

2. Common API Error Payloads

When an error occurs, the AdVanta API returns a structured JSON payload:

{
    "status": false,
    "error_code": "INVALID_API_KEY",
    "message": "The provided app apiKey is invalid or inactive.",
    "timestamp": 1718000000
}

3. Postback Simulator & Debugger Tool

Test your server callback endpoint without having to complete real offers:

Navigate to your Publisher Dashboard → Apps → App Details.
Click on the Test Postback tab.
Enter test values for userId and payout, then click Send Test Postback.
Inspect your server's exact HTTP response code and payload in the live inspector.