Update a client-side token
Updates a client-side token using its ID.
You can revoke a client-side token by changing its status
to revoked
. Client-side tokens that are revoked can't be updated to active
.
If successful, your response includes a copy of the updated client-side token entity.
Path Parameters
Paddle ID of the client-side token entity.
Request Body
Status of this client-side token.
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.
1231{
2 "status": "revoked"
3}