In the event of an error the APT.MobileAPI will return an HTTP status code. The table below details how these HTTP status codes relate to errors you may encounter using the APT.MobileAPI.
| HTTP Status Code | HTTP Description | APT.MobileAPI Description | APT.MobileAPI Reason |
|---|---|---|---|
| 400 |
BadRequest |
Request cannot be null |
The request data is empty or invalid |
| 403 |
Forbidden |
Invalid Customer Key |
The Customer Key is invalid |
| 403 |
Forbidden |
Invalid API Key |
The API Key is invalid or expired |
| 404 |
NotFound |
Facility unavailable |
The parking facility is not connected to the Bridge application. If this issue persists please contact APT SKIDATA |
| 405 |
MethodNotAllowed |
Function not permitted at this facility |
The API Key you are using is not authorised to perform this function |
| 406 |
NotAcceptable |
The format of barcode content is not recognised |
The API Key you are using is not authorised to perform this function |
| 408 |
RequestTimeout |
Request timed out |
The parking facility did not respond to the request. If this issue persists please contact APT SKIDATA |
| 412 |
PreconditionFailed |
Ticket not present |
The ticket used in the request is incorrect, or is no longer present in the parking facility |
| 417 |
ExpectationFailed |
Error generating new API Key |
An internal error has occurred. If this issue persists please contact APT SKIDATA |
| 500 |
InternalServerError |
An error occurred while processing the request |
An unexpected error occured. If this issue persists please contact APT SKIDATA |
| 502 |
BadGateway |
No connection to bridge |
The web application is not connected to the Bridge application. If this issue persists please contact APT SKIDATA |
| 503 |
ServiceUnavailable |
Facility database offline |
The parking facility database is offline. If this issue persists please contact APT SKIDATA |