Errors
SocialData uses conventional HTTP response codes to indicate the success or failure of an API request. In general:
- Codes in the
2xx
range indicate success. - Codes in the
4xx
range indicate an error that failed given the information provided (e.g., a required parameter was omitted, Twitter user not found or suspended, etc.). - Codes in the
5xx
range indicate an error with SocialData servers (these are rare) — typically a retry will succeed.
HTTP STATUS CODE SUMMARY
200 | OK | Everything worked as expected. |
401 | Unauthorized | No valid API key provided. |
402 | Payment Required | Credits balance insufficient to process the request, add funds to your balance. |
403 | Forbidden | The API key doesn't have permissions to perform the request. |
404 | Not Found | The requested resource doesn't exist. |
422 | Unprocessable Content | Validation failed. The request was unacceptable, often due to missing a required parameter. |
429 | Too Many Requests | Too many requests hit the API too quickly. We recommend an exponential backoff of your requests. |
500 | Server Errors | Something went wrong on SocialData's end (These are rare.) Typically a retry will succeed. |
502 | Server Errors | Something went wrong on SocialData's end. (These are rare.) |
503 | Server Errors | Something went wrong on SocialData's end. (These are rare.) |