Skip to content

Error codes

Errors can occur when interacting with the Reach platform. In any case, the ouput of your request would contain the appropriate errorCode and errorMessage that best describe the encountered issue, if any.

The error codes defined by Reach Authentix API are summarized in the table below:

Error codeError description
400Bad Request
403Request Forbidden
404Resource Not Found
429Too Many Requests
503Internal Error
10002Missing Request Data
10003Accept Media Type Error - Requests should have 'Accept' Header set to 'application/json'
20002Authentication Error - Missing Request Authentication Headers
20003Authentication Error - Bad Credentials
20004Authentication Error - Multiple Users Associated to Credentials
20005Authentication Error - The requested applet is deactivated and can't be modified
20006Invalid page size. It cannot be zero or negative.
20007Invalid page number. It cannot be zero or negative.
20208Too many requests.
20209Timeout exceeded.
20210Internal server error.
40000Entity ID Generation Issue
40001Operation is not available with API Test Key
40002Name is empty
40003Invalid code length
40004Invalid expiry time
40005Invalid max trials
40006Name already exists for the undelying entity type.
40007Unknown SMS message template ID
40008Unknown message template ID
40009Unknown SMTP Setting ID
40010Unknown Configuration ID
40011No Effective update occurred due to empty or similar parameter set.
40012Invalid max controls.
40013Unknown Authentication ID
40014Unknown Authentication Trial ID
40015Unknown Authentication Trial Stats
40016No Authentication found
40101dest and channel parameters are required
40102Invalid authentication channel
40103Invalid destination for the provided channel. Phone numbers must be in E.164 format
40104A template data map must represent a valid Stringfied JSON Map.
40105Custom code should only contain numeric characters
40106Custom codes are not allowed by the configuration
40107Payment info is required
40108Invalid payment info
40109Configuration with no SMTP Setting defined for sending Email based authentications
40110Unknown message template ID or invalid messasge template for the specified channel
40111Mismatch between message template and Payment info
40112Custom variable definition missing
40113Invalid sender Email
40114An authentication already exist for the specified destination with a different channel
40115Mismatch between existing authentication and current trial on the Payment info data
40116Issue with SMS delivery
40117Issue with Email delivery
40118Only Applet Owner email address is allowed at test time
40119Invalid authentication status
40120Invalid update authentication status
40121Invalid destination. Either Phone or email. Phone numbers must be in E.164 format
40122Invalid Authentication Trial Status
40123Either the Authentication ID or the destination is required
40124Code is required
40125Mismatch on digital payment data when controling an authentication
40126Insufficient funds
40127Authentication control issue