Getting Started

Error Handling

8min

Response Codes

We use the following status code in the response depending on the success or failure:
Status Code
Description
200 - ✅ Success/OK
Request success and the response will return with the requested data.
400 - ❌ Bad Request
The request returned an error.
401 - ❌ Unauthorized
The credentials are not valid.
403 - ❌ Forbidden
You don't have permission to perform the request.
404 - ❌ Not Found
The requested resource can't be found.
500 - ❌ Internal Server Error
Web server is experiencing problems, but it can't pinpoint the specific error or its root cause.
Troubleshoot
Here is our recommendation in terms of handling errors:
400 - Bad Request Error
JSON
{
    "status": 400,
    "error_code": 3,
    "message": "Bad Request",
}
{
    "status": 400,
    "error_code": 3,
    "message": "Bad Request",
}
﻿
﻿Cause
The bad request error occurs when the user sends an incorrect or invalid data like invalid password or invald data.
400 - UserDoesnotExistError
JSON
{
    "status": 400,
    "error_code": 21,
    "message": "User does not exist.",
}
{
    "status": 400,
    "error_code": 21,
    "message": "User does not exist.",
}
﻿
﻿Cause
The user doesnot exist error occurs if user try to login with incorrect credentials.
400 - AirWaybillAlreadySubscribedError
JSON
{
    "status": 400,
    "error_code": 30,
    "message": "Air Waybill is already subscribed with same awb number",
}
{
    "status": 400,
    "error_code": 30,
    "message": "Air Waybill is already subscribed with same awb number",
}
﻿
﻿Cause
System shows error if user try to repost the already existing air waybill number.
400 - ContainerAlreadySubscribedError
JSON
{
    "status": 400,
    "error_code": 10,
    "message": "Container is already subscribed with same mbl number",
}
{
    "status": 400,
    "error_code": 10,
    "message": "Container is already subscribed with same mbl number",
}
﻿
﻿Cause
System shows error if user try to repost the already existing container number and mbl number.
500 - Internal Server Error
JSON
{
    "status": 500,
    "error_code": 1,
    "message": "Internal server error",
}
{
    "status": 500,
    "error_code": 1,
    "message": "Internal server error",
}
﻿
﻿Cause
Web server is experiencing problems, but it can't pinpoint the specific error or its root cause.
500 - TemporarySubscriptionUnavailableError
JSON
{
    "status": 500,
    "error_code": 11,
    "message": "Temporarily subscription unavailable for this carrier",
}
{
    "status": 500,
    "error_code": 11,
    "message": "Temporarily subscription unavailable for this carrier",
}
﻿
﻿Cause
It's not you, it's us. This error means we have suspended the subscription for the particular carrier temporarily
✉️ Need some help?
If you encounter a problem or require assistance, please contact our support team with details regarding your request at [email protected]. A representative will connect with you soon. 😊

Status Code	Description
200 - ✅ Success/OK	Request success and the response will return with the requested data.
400 - ❌ Bad Request	The request returned an error.
401 - ❌ Unauthorized	The credentials are not valid.
403 - ❌ Forbidden	You don't have permission to perform the request.
404 - ❌ Not Found	The requested resource can't be found.
500 - ❌ Internal Server Error	Web server is experiencing problems, but it can't pinpoint the specific error or its root cause.

Updated 25 Mar 2024

Did this page help you?

Terminology

Supported Carriers