Skip to main content
For most use cases, the slideless CLI is easier. The CLI command is slideless pin <presentationId> <tokenId> --to-version <N> or --latest.

​
Endpoint

POST https://europe-west1-slideless-ai.cloudfunctions.net/setTokenVersionMode

​
Auth

HeaderValue
AuthorizationBearer cko_… (or cka_…) — must belong to the presentation’s owner
Content-Typeapplication/json
Required scope: presentations:write.

​
Request body

FieldTypeRequiredDescription
presentationIdstringyesPresentation the token belongs to
tokenIdstringyesToken to change
versionModeobjectyesEither {"type":"latest"} or {"type":"pinned","version":N}
Pinning rules:
  • version must be a positive integer
  • version must not exceed currentVersion
  • The token must not be revoked
Example — pin: 
{
  "presentationId": "0192f1c3-...",
  "tokenId": "0192f1c3-abcd-...",
  "versionMode": { "type": "pinned", "version": 3 }
}
Example — unpin (follow latest): 
{
  "presentationId": "0192f1c3-...",
  "tokenId": "0192f1c3-abcd-...",
  "versionMode": { "type": "latest" }
}

​
Response (200)

{
  "success": true,
  "data": {
    "success": true,
    "versionMode": { "type": "pinned", "version": 3 }
  }
}

​
Errors

StatusCodeCause
400invalid-argumentBad versionMode shape, version > currentVersion, or missing fields
401unauthenticatedMissing/invalid API key
403permission-deniedKey lacks presentations:write, or not the presentation’s owner
404not-foundpresentationId or tokenId doesn’t exist
410revokedCannot modify a revoked token

​
Concept reminder

Recipients cannot see past versions by URL manipulation — there is no ?v=N query parameter. Pinning is how the owner decides what a specific recipient sees, and that decision can only narrow: a latest token sees the current version; a pinned token is frozen. See Versioning.

​
Next