Introduction Last updated: 2023-11-25
Welcome to the Quickverify API documentation! This comprehensive guide is designed to assist developers in integrating and utilizing our robust verification services seamlessly. Our API empowers your applications with the capability to perform various verifications, including National Identification Number (NIN), Corporate Affairs Commission (CAC) details, Tax Identification Number (TIN), Bank Verification Number (BVN), and more..
Getting Started
1. Login or Create an Account: Input your details on quickverify.com.ng/signin to either login or sign up as a customer if you have no account already.
2. Retrieve your API keys: When you integrate with our services, you will need to authenticate using your api key. Go to your profile page, navigate to API keys and copy the key to make your first API call.
3. Fund your wallet: Top up your wallet to avoid service disruption. You can fund your wallet on your portal via bank transfer or online payment.
Response Codes & Status
When using the Quickverify API, you may encounter custom response codes that indicate the status of a particular request. These custom response codes are as follows:
00 | Successful | This code indicates that the request was successful and that the expected data has been returned. |
01 | Record not found | This code indicates that the ID provided in the request was not found in the system. |
02 | Service is not available | This code indicates that the requested service is unavailable. This could be due to maintenance, downtime, or other issues. |
It is important to note that custom response codes only compliments the standard HTTP response.
Response Structure
{
"status": false,
"response_code": "01",
"message": "Record not found",
"verification": {
"reference": "254d1801-db5d-450a-954b-3682ddae7072"
},
"session": {}
}
{
"status": false,
"detail": "Verification failed",
"response_code": "02",
"message": "Verification can't be completed at this time. Kindly retry later",
"verification": {
"reference": ""
},
"session": {}
}
Authentication
Quickverify authentication mechanism relies on just one type of key.
All API calls on Quickverify can be executed using the secret key. No other Authorization header should be implemented when calling Quickverify's API endpoints
Need Assistance?
This documentation may not be as clear as we hoped. We encourage you to contact us so we can be sure your needs are being met! You can contact us on developer@quickverify.com.ng
Glad to have you here!