FAQs

An API (Application Programming Interface) enables communication between different applications. APIs provide access to data, allow application integration, extend functionality, and enable automation. They are used to create web, mobile, and desktop applications quickly and efficiently.

Depending on the API being used, XYZ's API can provide various types of data in JSON format. For KYC, the API responses will indicate a Match, No Match, or Partial Match for each field parameter where values are passed. Understanding the available data and how to access it requires a careful review of the API documentation.

Updates may occur more frequently if necessary. It is important to note that some endpoints may be updated more frequently than others depending on the data source. It is recommended to check the documentation regularly to stay informed about any updates or changes to the API

Yes, authentication is required to use the API service. The API uses Token-based authentication to ensure that only authorized users can access the API endpoints. Please click here to check our Token generation process.

Common error codes that you might encounter include 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, and 500 Internal Server Error. Each of these codes indicates a different type of error, such as a problem with the request syntax, an authentication issue, or a server-side issue. Please click here for our documentation.

If you are experiencing unexpected results from an API request, you should contact our support team at support (at) idmerit.com or raise a ticket here. Our team can assist you in diagnosing and resolving the issue.

We appreciate your input. To suggest enhancements for our API service, please contact us at support (at) idmerit.com or raise a support ticket here. Thank you.

Our KYC verification API allows you to verify a person by providing their First Name, Last Name, date of birth, and other identifying details. The API will then match this information against relevant databases and sources to confirm the person's identity. Depending on the company and industry, the criteria for successful verification may vary. For instance, a gaming platform may use a match on Name + date of birth to verify a person's identity by performing an AGE verification. The match response against each input parameter can help determine success or failed verification.

Yes, please refer to our documentation. https://idmkyc-doc.idmerit.com/

Yes, there are restrictions or limitations on the use of our API service. These limitations include:

• Rate limitations: To ensure security, we limit the number of request sessions per IP to two requests per second per IP (120 requests/minute/IP).

Yes, the API services are designed to integrate with other applications or services. As this is language-independent, this can be achieved by using the API's endpoints and incorporating them into your application's code. However, it's important to check the API's documentation for information on integration requirements.

The KYC API service can verify various types of personal information such as a person's name, date of birth, address, city, state, zip, and gender. Some APIs can also verify government-issued identification documents like driver's licenses or SSNs. The specific types of information that can be verified may vary depending on the API service. Please refer to our documentation for more information.

The accuracy and reliability rates of the API service can vary based on factors such as the quality of data input and the verification process. While it's difficult to provide a specific percentage without more information, the service is designed to provide a high level of accuracy and reliability to ensure the authenticity of identities.

If the Identity Verification API service is unable to verify a user's identity, an alternative verification method or options may be used such as using IDMscan.

The Identity Verification API service is designed to support multiple languages and regions, but availability may depend on the service provider or platform used to access the API. However, our response only provides a Match/No Match without any PII information