FAQs | API Developer Portal

1. How do I authenticate my requests to the encrypted version of the API?

Ans: Authentication methods can vary across APIs, commonly involving API keys or OAuth tokens. For the encrypted version of this API, authentication is done using header_secrets and a pass_key, which must be included in the request headers.

2. How will I receive the header_secrets and pass_key?

Ans: The header_secrets and pass_key will be shared with you separately via email by the ISU team.

3. What should I do if I encounter an error while using the API?

Ans: Errors may occur due to invalid input, authentication failures, or server issues. First, verify that your request is properly formatted and includes the correct authentication credentials. If the issue persists, please contact the iServeU support team for assistance.

4. How is secure data transmitted to and from the API?

Ans: iServeU ensures secure data transmission by using AES-256 encryption for both the request and response bodies. Additionally, encrypted headers (header_secrets) and a pass_key are used for authentication. It is essential to implement the encryption and decryption logic exactly as provided by iServeU to maintain security and compatibility.

5. What details can be verified using the iServeU Passport Verification API?

Ans: Refer to the API document for more information.

6. What happens if the Passport verification fails? What are the common reasons for failure?

Ans: Some failure scenarios are listed in the document; you can refer to them.

7. Can the iServeU Passport Verification API detect fraudulent or fake passports?

Ans: Yes, iServeU's Passport Verification API can detect fraudulent or fake passports using the passport number. Using the passport number, we’ll fetch the customer details associated with the passport and we can cross-check the details to ensure the provided information is correct or not.

8. Does iServeU store any of the passport data that is verified?

Ans: No, iServeU does not store any of the retrieved information related to the passport. We typically check with the authority database in real-time and share the details with the clients to complete the verification process. The data is not retained by iServeU.

9. What kind of support does iServeU provide for integrating and using the Passport Verification API?

Ans: iServeU typically provides API documentation and an implementation team to assist with integration. For persistent issues, you can reach out to their support team.

10. What are the prerequisites for using the Passport Verification API?

Ans: The main prerequisites are having the credentials provided by iServeU and the ability to implement the API calls, including the required encryption and decryption of headers and payload as per iServeU's specifications.

11. Can I perform bulk verification of passports using this API?

Ans: iServeU’s Passport Verification API is designed for single-record checks. If you have a requirement for bulk verification, you should contact iServeU directly to place your requirement and check the availability of such an option.