Error Codes
How we indicate errors
We use conventional HTTP Codes to indicate success or failure of a request.
To give further detail to any problem(s) that arise(s), we employ a special meta tag in every response containing a 3 or 4 digit response code.
Example (401-Response)
{
"meta": {
"code": 401,
"message": "Incorrect Username/Password was provided"
},
"data": {}
}
Example (404-Response, with 4040-expanded response)
{
"meta": {
"code":4040,
"message":"No Active Profiles Exist For This Account"
},
"data":{}
}
Error Codes Summary
Here is a summary of expected HTTP Status codes to expect on our system.
| HTTP Code | Description |
|---|---|
200 - OK | The requested transaction was successful |
400 - Bad Request | The request was not accepted, often due to missing a required parameter |
401 - Unauthorized | Incorrect credentials or missing API key |
402 - Request Failed | The parameters were valid, however the request failed |
403 - Forbidden | The associated account does not have the authorization to action the transaction |
404 - Not Found | The requested resource does not exist |
500, 502, 503, 504 - Server Errors | An issue occurred on inTime's end. Further instruction to be provided, should this occur |