Start Dedupe
Begin with a simple check to understand whether a borrower can proceed with participating lending partners. Share the borrower’s identifiers in the format configured for your application—hashed or unhashed—and Aarthik Labs starts the Dedupe check.
This is an optional first step. The response gives you a journey ID to carry through the application. Use Fetch Dedupe Results to view the outcome, then continue with Eligibility or Create A Journey using the same ID.
Authentication
Send Authorization: Bearer <PLATFORM_API_KEY> from a trusted back-end.
Path parameters
Stable borrower identity from the partner system. Keep a 1:1 mapping between the borrower and borrowerProviderID across sessions and application attempts to preserve resume, history, and post-disbursal continuity.
Headers
Start-attempt retry key. Use a fresh key for each new application attempt. Reuse the same key only when retrying the same Start request after a timeout or temporary failure. If omitted, the platform creates a fresh non-idempotent attempt with a server-generated internal key for compatibility; retries without a client key can create duplicate attempts.
Optional caller-supplied trace identifier. When omitted, the API generates one and mirrors it as correlation_id.
Query parameters
Request
Provide at least one of pan or mobileNumber. The identifier representation is configured for your application by Aarthik Labs; do not send a mode flag. Example hashes are synthetic opaque values, not an algorithm specification.