Clients & identity

Associate a person with the studio independently of a booking, or let supported admission create the association. Creating a client is not customer authentication or account activation.

Inputs and prerequisites

Create a client with at least email; names, phone and a studio-scoped source/external_id are optional. The default account_type=external links the normalized email to this studio.

Use current client creation authority and authorize the visitor in your backend. A matching global person retains their profile, credentials and login state; the response does not reveal their other studios.

Choose when to associate

Ordinary booking/purchase commands can accept email directly, so a separate create call is optional where admission supports association. Quote reads instead accept an owned client_id when personalization is needed; they do not accept email or create a client.

A Tour requiring phone needs an explicit owned-client create/update before admission, because the Tour body does not accept arbitrary shared profile fields. Use client update with current authority rather than silently adding unsupported booking fields.

Account activation is explicit

New external people cannot use Podyx sign-in while external. Client association and booking creation do not automatically send an activation invitation.

An authorized studio can request a standard account with the additional activation permission, or use activation requests with clients:request_activation. send_invitation=false retains a pending explicit request without email; it does not grant login.

Only the dedicated email-owner proof activates the same person and retains studio links and purchases. The customer follows the native activation confirmation. The proof is not a studio API-key login credential. A queued invitation does not establish delivery.

Results and recovery

Retain the real returned client ID for current profile, rights and booking association. A write needs a persisted UUID header. If its response is lost, retry the same command; do not create a second person to discover what happened. Read current client state with still-authorized credentials.