Documentation Index
Fetch the complete documentation index at: https://developer.prove.com/llms.txt
Use this file to discover all available pages before exploring further.
Definition
Prove publishes server-side SDKs for Go, Java, .NET, TypeScript, and JavaScript. Other stacks use the same HTTP operations documented under Reference (for examplePOST /v3/start, POST /v3/validate, POST /v3/challenge, POST /v3/complete).
Installation
Packages and dependency coordinates by language:Authentication
The SDKs authenticate to Prove with OAuth 2.0 using a client ID and client secret (for example from environment variables). Example client construction:Token lifetime: OAuth access tokens expire after 60 minutes; obtain a new token before expiry.
Next field
Responses include a Next value that indicates the next SDK or HTTP operation for the active flow.
Start()
Initiates a Prove flow. Accepts flow type, phone number, and optional challenge hints (often from a server route such as POST /initiate).
Required parameters
-
Flow type —
desktopormobile(device class for the flow). -
Final target URL — Required when
flowTypeisdesktop. Maximum length 128 characters. Instant Link redirects the customer to this URL after the link is opened.
Possession behavior by flow type
desktop: Instant Link performs the possession check.mobile: Mobile Auth when enabled, then OTP as fallback.
-
ssn— Full SSN or last four digits. May be supplied onStart()orChallenge(). -
dob— Date of birth:YYYY-MM-DD,YYYY-MM, orMM-DD. May be supplied onStart()orChallenge(). -
allowOTPRetry—trueallows up to three OTP entry attempts; defaultfalse.
Client behavior for OTP retries must match the Pre-Fill implementation guide — request new OTP code.
-
Auth token — Short-lived JWT for the current flow; passed to the client
Authenticate()method for possession checks. -
Correlation ID — Identifier for this flow; include on
Validate(),Challenge(), andComplete()for the same session. Correlation context expires 15 minutes afterStart()returns. Useful for troubleshooting. -
Next— Next operation to invoke.
Validate()
Validates possession after the client signals completion. Parameter: correlation ID from Start() (often from a server route such as POST /verify).
-
success—trueif mobile validation succeeded; otherwisefalse. -
challengeMissing— Whentrue, the flow requiresChallenge()with the collected inputs. - Phone number — Validated E.164 value when present.
-
Next— Next operation to invoke.
challengeMissing is true, collect SSN (last four or full) or DOB on the client unless those values were already sent on Start().
Challenge()
Runs when possession succeeded but identity challenge data is still required. Requires the correlation ID from Start() and the challenge fields (aligned with optional Start() parameters such as ssn and dob).
Complete()
Final verification call after the customer confirms or edits their information.
Parameters
-
Correlation ID — From
Start(); must match^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$. - Individual — Customer attributes as a structured map.
-
success—truewhen customer data is returned for the verification outcome. -
Next— In the terminal state,Done.
SDK source repositories: github.com/prove-identity. Use Watch on a repository for release notifications.

