Errors Codes
In the event of receiving an HTTP 40x response from a Short URL API request, the response body will contain a JSON document showing a response code and human readable error string.
{
"result_code": "100",
"result_message": "Un-parsable Request Document",
"client_reference": "...if provided during original request..."
}
Result Code List
| Result Code | Should Retry | Result Message |
|---|---|---|
| -4 | No | Unsupported Media Type |
| -3 | No | Not Acceptable |
| -2 | No | HTTP method not allowed |
| -1 | Yes | There has been an internal error! |
| 2 | No | Authentication Failure |
| 100 | No | Un-Parsable Request Document – The JSON request document supplied was not correctly formed |
| 101 | No | The request was missing a required remote_url field |
| 102 | No | The request contained a badly formed URL in remote_url field |
| 103 | No | The new masked url does not include a valid account id for required credentials |
| 104 | No | That combination of query parameters is not possible |
| 106 | No | Cannot add a short-url enterprise config for this enterprise/entity/year/month - it already exists |
| 107 | No | You already have the maximum number of currently active short-urls active on this account |
| 108 | No | The valid_until_date value is too far in the future |
| 109 | No | The valid_until_date value must be in the future |
| 110 | No | The valid_until_date value is not far enough in the future |
| 404 | No | Not found |
| 412 | No | Stale update entity |
Note: First four result codes have Negative values