Posting API - Error Codes & Responses
HTTP Status Codes
The Showtime Analytics API attempts to return appropriate HTTP status codes for every request.
| Code | String | Description |
|---|---|---|
| 200 | OK | Message successfully received, added to queue for processing |
| 400 | Bad Request | The XML in the request was invalid or the structure was invalid. Complete message is rejected. |
| 401 | Unauthorized | Authentication credentials were missing or incorrect. Complete message is rejected. |
| 500 | Internal Server Error | Something is broken. We have been notified. Try again later. If the problem persists, please contact support. Complete message is rejected. |
| 503 | Service Unavailable | The Showtime Analytics servers are up, but overloaded with requests. Try again later. Complete message is rejected. |
Processing Response Messages
Once the Showtime Analytics API has successfully received your request, it will processes each entity in the message separately and returns a separate status for each update. The responses for each entity will be returned in the same message structure as the request.
When there is a processing error, there will be a descriptive error text plus a machine-parseable code. While the text for an error message may change, the codes will stay the same.
The following table describes the codes which may appear when working with the API:
| Code | String | Description |
|---|---|---|
| 0 | Successfully Processed | |
| 100 | Internal Error | Entity could not be processed because there was an unexpected error in the processing system. This error will only be returned after it has been retried multiple times. That specific entity update is rejected. |
| 101 | Invalid entity | Entity could not be processed because the structure was invalid or the datatype for some field(s) did not match the spec. That specific entity update is rejected. |
| 102 | Missing Data | Entity could not be processed because some madatory field(s) was missing/empty. That specific entity update is rejected. |