Create a client-side token
Creates a new client-side token.
If successful, your response includes a copy of the new client-token entity.
Request Body
Short name of this client-side token. Typically unique and human-identifiable.
Short description of this client-side token. Typically gives details about what the token is used for and where it's used.
Response
Represents a client-side token entity.
Unique Paddle ID for this client-side token entity, prefixed with ctkn_. Not used for Paddle.js authentication; use token for authentication.
A client-side token, prefixed with test or live depending on the environment of your account. Pass as the token parameter when initializing Paddle.js to authenticate.
Short name of this client-side token. Typically unique and human-identifiable.
Short description of this client-side token. Typically gives details about what the token is used for and where it's used.
Status of this client-side token.
RFC 3339 datetime string of when this client-side token was revoked. null if not revoked.
RFC 3339 datetime string of when this entity was created. Set automatically by Paddle.
RFC 3339 datetime string of when this entity was updated. Set automatically by Paddle.
Information about this response.
Unique ID for the request relating to this response. Provide this when contacting Paddle support about a specific request.
12341{
2 "name": "Pricing page integration",
3 "description": "Used to display prices and open checkout within our pricing page on our marketing domain."
4}