Errors
Whenever any Flit endpoint request doesn't return 2** HTTP status code, this means an error has occurred. The error could be from your end (payload sent to us), or from our system. Below are the notable errors that can be returned:

Validation Error β€” 422

This error code is returned when the payload you sent doesn't meet with the required parameters. Here is a sample request validation error:
{
"error": [
{
"vehicle": "value is not a valid enumeration member; permitted: 'BIKE', 'CAR', 'VAN', 'MINI_VAN'"
}
]
}

Authentication Error β€” 401

This error code is returned when a request doesn't contain the right Authorization API Key. See the Authentication section on how to properly authenticate your requests. Here is a sample authentication error:
{
"detail": "Could not validate credentials"
}

Access Forbidden Error β€” 403

An access forbidden error is returned when you don't have the permission to access the requested resources. Here is an example error:
{
"detail": "You do not have the priviledge to access this resource."
}

Insufficient Funds Error β€” 406

An insufficient funds/balance error is returned when you try to pay for a shipment with insufficient amount in your wallet. Here is an example error message:
{
"detail": "Your balance is too low to perform this transaction, please fund and try again"
}

Not Found Error β€” 404

A "Not Found" error is returned when you try to access a resource that does not exist. Here is an example error:
{
"detail": "Order not found"
}

Internal Server Error β€” 500

An internal server error is returned when something goes wrong on our side. Here is an example error message:
{
"detail": "Something went wrong on our side. We've received the notification and working on fixing it, please try again later"
}
Copy link
On this page
Validation Error β€” 422
Authentication Error β€” 401
Access Forbidden Error β€” 403
Insufficient Funds Error β€” 406
Not Found Error β€” 404
Internal Server Error β€” 500