List of API error codes

The root cause of errors can be generalised from the HTTP Response Code. The list below details the errors that could occur during an integration or in production.

HTTP Status Code	Name	General Guidelines
400	Bad Request	Check the payload or params
401	Unauthorized	Check the auth credentials
403	Forbidden	The credentials provided do not have access to the resources requested
404	Not Found	The requested resource does not exist
405	Method Not Allowed	Check the HTTP Request Type and check the Content-Type Header
429	Too Many Requests	Check that there are not too many requests being sent to the server
500	Internal Server Error	Needs to be raised to the Pay1st Implementation Manager

Error Format

All error messages typically consist of an errorMessage field and an errorCode field.

Response Field	Description
errorMessage	A message detailing the error that occurred
errorCode	A code to identify the error source
sessionId	A session identifier for the request. This will need to be sent to the Pay1st Implementation Manager to make troubleshooting API request issues easier

All error responses return a 4xx error HTTP status.

{
   "errorMessage": "ERROR_MESSAGE",
   "errorCode": "ERROR_CODE",
   "sessionId": "SESSION_ID"
}

List of Error Codes

There are two classes of Error Codes in User Validation

Errors from the Product itself (e.g. for direct topup - the playerID is a blocked account)
Errors from the Flow1st platform

The below is the possible list of errors from the Flow1st platform. This list is non exhaustive, feel free to ask the Flow1st team if you encounter a different error than one in the list

Code	Message	Description
0010	System error. Please contact System Administrator.	This needs to be forwarded to the Carry1st team
0101	You have no access to this resource.	Check your credentials and that your token is valid when using this endpoint
0219	This order is currently processing.	The Order is currently processing (if the external reference was sent twice by the partner, then this is a valid error. If it was only sent once then it should be sent to Carry1st team)
0371	Product bundle does not exist for distributor.	The Product Bundle is not enabled for your account (if using multiple accounts, check that the correct credentials are used)
0374	Product bundle is not active.	The Product Bundle is not available
0451	Product fulfilment channel does not exist.	This needs to be forwarded to the Carry1st team
0601	Product bundle does not exist.	The Product Bundle is not available
0602	Sorry, you can only purchase this item 1 time every 164 days.	A purchase time limit has been configured on the Product Bundle
0607	Sorry, you cannot purchase this item. Next eligible purchase date Jun 15, 2026 at 12:00 AM UTC.	A purchase time limit has been configured on the Product Bundle
1100	Distributor has insufficient balance.	There is insufficient balance for this order
1101	Distributor request has the wrong format.	The signature is in the incorrect format (most likely pre-integration) An expired token is being used to generate the signature (most likely post-live integration)
1102	Insufficient distributor balance to complete fulfilment for this order.	There is insufficient balance for this order
1105	Product bundle is out of stock.	The Product Bundle is out of stock
1107	Provider is out of stock.	The provider of the Product Bundle is out of stock
1109	recipientIdentifier does not match the expected format.	The `recipientIdentifier` field does not match its expected pattern. Typically this is a regex or email pattern that is not being satisfied