pixel

Dev Provision Pixel

Provision a pk_ + scoped sk_live_ pair for a client account by email.

Internal tool for onboarding: keys land under the target user's account (the multi-tenancy boundary), while auth is the dev's own token — no client password or JWT needed. Idempotent: reuses an active pixel key for the same domain/label and an active scoped server key when its secret is re-displayable; pass new_server_key to force a fresh secret.

post/api/v1/pixel/dev/provision

Request

  • Base URL: https://api.trylapis.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.trylapis.com/api/v1/pixel/dev/provision
  • Auth: HTTP bearer

Request body

emailstring required

Email of the Lapis user account to provision for

client_namestring required

Brand/client name used in key labels (e.g. 'Duradry')

domainstring nullable

Restrict the browser key to this domain (recommended; subdomains included). Comma-separated for several, e.g. 'example.com, example.ca'

new_server_keyboolean

Force-create a new server key even if an active scoped one exists

Response

Successful Response

user_idinteger required
emailstring required
pixel_key_idinteger required
pixel_keystring required
pixel_key_createdboolean required
server_key_idinteger required
server_keystring nullable

Raw sk_live_ secret. Null only if an existing key predates encrypted storage; rerun with new_server_key=true.

server_key_prefixstring required
server_key_createdboolean required

Changes

No recorded changes to this operation across all 1 revision of this API.