Response Format
All agntdata API responses follow a consistent format. Successful responses:HTTP Status Codes
| Status | Meaning |
|---|---|
200 | Success |
400 | Bad Request — Invalid parameters |
401 | Unauthorized — Invalid or missing API key |
404 | Not Found — Resource or endpoint doesn’t exist |
429 | Too Many Requests — Rate limit exceeded |
500 | Internal Server Error — Something went wrong |
Error Codes
Authentication Errors
| Code | Description | Solution |
|---|---|---|
UNAUTHORIZED | Invalid or missing API key | Check your API key is correct |
INSUFFICIENT_CREDITS | Not enough credits | Top up your credit balance |
Request Errors
| Code | Description | Solution |
|---|---|---|
VALIDATION_ERROR | Required parameter missing or invalid | Check the API reference for required params |
ENDPOINT_NOT_FOUND | Endpoint doesn’t exist | Verify the endpoint path |
PROVIDER_NOT_FOUND | Platform not available | Check available platforms |
Rate Limit Errors
| Code | Description | Solution |
|---|---|---|
RATE_LIMITED | Too many requests | Wait and retry with backoff |
Data Errors
| Code | Description | Solution |
|---|---|---|
NOT_FOUND | Resource doesn’t exist | Verify the username/ID is correct |
PROVIDER_ERROR | Upstream platform error | Retry later |
PROVIDER_UNAVAILABLE | Platform temporarily unavailable | Retry later |
Server Errors
| Code | Description | Solution |
|---|---|---|
INTERNAL_ERROR | Unexpected server error | Retry, contact support if persistent |
CONFLICT | Resource conflict | Check for duplicate resources |
Handling Errors
JavaScript/TypeScript
Python
Retry Strategy
For transient errors, implement exponential backoff:Next Steps
Rate Limits
Understand rate limits and how to stay within them.
API Reference
Browse endpoint documentation.