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 DL Verification API?

Ans: Please refer to the official API documentation for a complete list of verifiable details.

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

Ans: Some common failure scenarios are outlined in the API documentation. Please refer to it for more information and troubleshooting guidance.

7. Can the iServeU DL Verification API detect fraudulent or fake driving licenses?

Ans: Yes, the API can detect fraudulent or fake driving licenses using the DL number. It fetches the customer details associated with the DL, allowing for cross-verification to ensure the provided details are accurate.

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

Ans: No, iServeU does not store any retrieved DL information. The API performs real-time checks with the authoritative database and shares the results with the client without retaining the data.

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

Ans: iServeU provides detailed API documentation and support from the implementation team. For ongoing or critical issues, you can contact their support team for assistance.

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

Ans: You must have valid credentials provided by iServeU and the capability to implement API requests, including the required encryption and decryption of headers and payloads as per iServeU’s specifications.

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

Ans: The DL Verification API is primarily designed for single-record checks. For bulk verification needs, please reach out to iServeU to discuss available options.