Mint a publish/unpublish request token
Changed onMints a short-lived, opaque "request token" the app's creator surface forwards to Fanvue to ask the creator to confirm a publish or unpublish.
The token is bound to the calling app (a token can only be minted for the app whose credentials make the call — otherwise 403) and to the acting creator, so it can only drive that creator's native confirmation modal.
A publish request may narrow the access modes the creator is offered with `allowedAccessModes`; an incoherent constraint (empty, duplicated, or not containing `proposedAccessMode`) is rejected with 400 and a message naming the rule it broke.
post/experiences/request-token
Request
- Base URLhttps://api.fanvue.com
- URLhttps://api.fanvue.com/experiences/request-token
- AuthOAuth 2Authorization code: https://auth.fanvue.com/oauth2/authToken URL: https://auth.fanvue.com/oauth2/token scopes: write:experience
Headers
X-Fanvue-API-Versionstring required
Example:2025-06-26
API version to use for the request
Request body
Example request
{
"imageUrl": "https://example.com/covers/launch-your-page.jpg",
"allowedAccessModes": [
"FREE"
],
"proposedActions": [
{
"externalActionId": "spin",
"title": "Spin the wheel",
"suggestedPriceCents": 500
}
],
"proposedExperienceType": "GAME"
}Response
The minted request token
Example response
{
"token": "req_2f1c…"
}Changes
- info
added the new optional request property
/
- info
- breaking
added
subschema #3to the response bodyoneOflist for the response status - warning
the
/request property's maxLength was set to500 - warning
the
/request property's maxLength was set to255 - warning
the
/request property's maxLength was set to100 - info
added the new optional request property
/ - info
added the new optional request property
/
- breaking