Prembly API – Response Codes & Verification Status

Client Documentation · HTTP & Custom Response Codes · Prepared for Client Reference

HTTP CodeCategoryMeaning / Short LabelExplanationExample Response BodyNotesCustom Code
2002XXOK / SuccessfulThe request was successful and the expected data has been returned.{"status": true, "response_code": "00", "data": { ... }}Standard success. Check response_code field for Prembly-specific status.00
2002XXRecord Not Found (Soft)Request succeeded at HTTP level but the ID was not found or may be incorrect in the Prembly system.{"status": true, "response_code": "01", "message": "Record not found"}Prembly returns HTTP 200 even when a record is not found. Check response_code.01
2002XXService Unavailable (Soft)Verification cannot be completed at this time. The service may be under maintenance or temporarily down.{"status": true, "response_code": "02", "message": "Verification can't be completed, retry later"}Retry with exponential back-off. Monitor Prembly status page.02
2002XXInsufficient Wallet BalanceThere is insufficient balance in the wallet to complete the transaction.{"status": false, "response_code": "03", "message": "Insufficient wallet balance"}Top up wallet before retrying.03
2002XXBlocked / Watch-listedApplicable to the BVN endpoint. The BVN provided has been flagged/blocked.{"status": false, "response_code": "07", "message": "BVN is blocked/watch-listed"}BVN-specific. Do not retry with same BVN.07
4004XXBad RequestThe request was malformed or missing required parameters.{"status": false, "message": "Bad request: missing required field 'id_number'"}Validate all required fields before sending.-
4014XXUnauthorizedAuthentication credentials are missing or invalid.{"status": false, "message": "Unauthorized: invalid API key"}Verify API key is correctly set in the Authorization header.-
4034XXForbiddenThe authenticated client does not have permission to access this resource or endpoint.{"status": false, "message": "Forbidden: you do not have access to this resource"}Contact Prembly support if access should be granted.-
4044XXNot FoundThe requested endpoint or resource does not exist.{"status": false, "message": "Not found: endpoint does not exist"}Verify the endpoint URL against the latest API documentation.-
4054XXMethod Not AllowedThe HTTP method used (e.g., GET vs POST) is not supported for this endpoint.{"status": false, "message": "Method not allowed"}Check API docs for the required HTTP method per endpoint.-
4224XXUnprocessable EntityThe request was well-formed but contained semantic errors (e.g., invalid ID format).{"status": false, "message": "Validation error: id_number must be numeric"}Review field formats and constraints in the API docs.-
4294XXToo Many RequestsRate limit exceeded. The client has sent too many requests in a given time window.{"status": false, "message": "Rate limit exceeded. Try again in 60 seconds."}Implement rate-limiting logic and exponential back-off on the client side.-
5005XXInternal Server ErrorAn unexpected error occurred on the Prembly server side.{"status": false, "message": "Internal server error. Please try again later."}Log the request ID and contact Prembly support if persistent.-
5025XXBad GatewayPrembly's server received an invalid response from an upstream service.{"status": false, "message": "Bad gateway"}Usually transient. Retry after a short delay.-
5035XXService UnavailableThe server is temporarily unable to handle requests (overload or maintenance).{"status": false, "message": "Service temporarily unavailable"}Check Prembly status page. Retry with back-off.-
5045XXGateway TimeoutThe upstream service did not respond in time.{"status": false, "message": "Gateway timeout"}Retry after delay. If frequent, report to Prembly.-