Complete customer registration
Create a customer from a verified phone registration session and issue authentication tokens. The operation is atomic and idempotent on the registration session token: an identical retry replays the original successful response without creating another account. The registration session token remains the replay identity even when a retry uses a new Idempotency-Key header.
Headers
Body
The required information for completing customer registration.
The session token returned after verifying an unregistered phone.
32 - 512The customer's given name.
1 - 55The customer's surname.
1 - 55The customer's required but initially unverified registered fallback email address. It may receive email OTP fallback for future sign-ins, and a successful email OTP verifies ownership.
6 - 100How much of the customer's surname barbers may see. When omitted, the full surname is visible.
full, initial Response
Created.
The JSON representation of issued authentication tokens as the result of a successful authentication challenge or the exchange of a refresh token.