post
https://api.cert.zerohash.com/client_auth_token
Generates a temporary JWT access token used to initialize zerohash SDK modules on behalf of one of your end users. The platform authenticates to this endpoint with its own HMAC credentials; the returned JWT is then handed to the end-user client.
Identifying the end user:
- The Onboarding SDK accepts
emailto start a fresh onboarding, orparticipant_codeto resume an existing user from where they dropped off. For a retry, sendemailandparticipant_codetogether — zerohash resolves the existing participant and the SDK comes up pre-filled (it is notparticipant_codealone). - All other SDK experiences require
participant_code(the user already exists).
Choosing a variant: the request body is an anyOf — pick the variant matching the SDK experience you are launching, set permissions accordingly, and include only that variant’s fields.
💡 Use the schema dropdown / per-variant examples on the request body below to load a ready-made payload for each experience.
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…