> ## Documentation Index > Fetch the complete documentation index at: https://api.fanvue.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # List an experience's priced actions > Returns the priced actions the creator has configured on one of your experiences, so your surface can render its own buttons with the real price — "Spin — $7" — instead of guessing. Owner app only: the experience must belong to the app whose credentials make the call, otherwise 403. Actions the creator has withdrawn are omitted. `amount` is in minor units (cents) and is resolved from Fanvue on every request, so a re-priced action is correct on the next read with no republish. An empty `actions` array means the creator has priced nothing; a failure to read the catalogue is a 502, never an empty list. > [!NOTE] > > **Required scope** > > * `read:experience` — Exchange a fan's experience token for the resolved experience and the fan's identity, so an embedded fan-facing experience can render the right content. ## OpenAPI ````yaml /openapi-v1.json get /v1/experiences/{experienceUuid}/actions openapi: 3.1.0 info: title: Fanvue API version: '0.1' servers: - url: https://api.fanvue.com security: [] paths: /v1/experiences/{experienceUuid}/actions: get: summary: List an experience's priced actions description: >- Returns the priced actions the creator has configured on one of your experiences, so your surface can render its own buttons with the real price — "Spin — $7" — instead of guessing. Owner app only: the experience must belong to the app whose credentials make the call, otherwise 403. Actions the creator has withdrawn are omitted. `amount` is in minor units (cents) and is resolved from Fanvue on every request, so a re-priced action is correct on the next read with no republish. An empty `actions` array means the creator has priced nothing; a failure to read the catalogue is a 502, never an empty list. operationId: listExperienceActions parameters: - $ref: '#/components/parameters/ApiVersionHeader' - schema: type: string format: uuid example: 00000000-0000-4000-8000-000000000010 required: true name: experienceUuid in: path responses: '200': description: The experience's active priced actions content: application/json: schema: type: object properties: actions: type: array items: type: object properties: externalActionId: type: string description: >- The app's own stable key for the action, as it declared it. example: spin title: type: string description: >- Creator-facing label, shown in the native payment dialog. example: Spin the wheel status: type: string enum: - active description: >- Always `active`. An action the creator has withdrawn is omitted from this read entirely, never returned as disabled. example: active amount: type: integer description: >- Price in minor currency units (cents), resolved from Fanvue at read time. Re-pricing is visible on the next read. example: 700 currency: type: string description: ISO 4217 code of the amount. USD only today. example: USD required: - externalActionId - title - status - amount - currency description: >- The experience's active priced actions, in the order the creator arranged them. required: - actions example: actions: - externalActionId: spin title: Spin the wheel status: active amount: 700 currency: USD - externalActionId: reveal title: Reveal a card status: active amount: 250 currency: USD '400': description: >- Bad Request - API version not supported OR validation failed OR invalid UUID content: application/json: schema: oneOf: - $ref: '#/components/schemas/UnsupportedVersionError' - $ref: '#/components/schemas/ValidationError' - $ref: '#/components/schemas/InvalidUuidError' '401': $ref: '#/components/responses/UnauthorizedResponse' '403': $ref: '#/components/responses/UnauthorizedResponse' '404': description: Experience not found content: application/json: schema: type: object properties: message: type: string '410': $ref: '#/components/responses/SunsetVersionResponse' '429': $ref: '#/components/responses/RateLimitResponse' '502': description: Failed to read the action catalogue from the upstream content: application/json: schema: type: object properties: message: type: string '503': description: Developer API upstream is not configured content: application/json: schema: type: object properties: message: type: string security: - BearerAuth: - read:experience components: parameters: ApiVersionHeader: name: X-Fanvue-API-Version in: header required: true schema: type: string default: '2025-06-26' example: '2025-06-26' description: API version to use for the request schemas: UnsupportedVersionError: type: object properties: error: type: string message: type: string required: - error - message description: API version not supported ValidationError: type: object properties: errors: type: array items: type: string required: - errors description: Request validation failed InvalidUuidError: type: object properties: message: type: string required: - message description: Invalid UUID format provided responses: UnauthorizedResponse: description: Unauthorized Response content: application/json: schema: type: object properties: error: type: string required: - error SunsetVersionResponse: description: API version no longer supported (sunset) content: application/json: schema: type: object properties: error: type: string message: type: string nextVersion: type: string required: - error - message RateLimitResponse: description: Too many requests - rate limit exceeded headers: Retry-After: description: Number of seconds to wait before retrying the request schema: type: integer X-RateLimit-Limit: description: The maximum number of requests allowed in the current window schema: type: integer X-RateLimit-Remaining: description: The number of requests remaining in the current window schema: type: integer X-RateLimit-Reset: description: The Unix timestamp (seconds) when the rate limit window resets schema: type: integer content: application/json: schema: type: object properties: error: type: string required: - error securitySchemes: BearerAuth: type: oauth2 description: >- OAuth 2.0 access token, presented as a JWT bearer token in the `Authorization` header. Obtain a token via the authorization-code flow; the scopes granted to the token determine which operations it may call. flows: authorizationCode: authorizationUrl: https://auth.fanvue.com/oauth2/auth tokenUrl: https://auth.fanvue.com/oauth2/token refreshUrl: https://auth.fanvue.com/oauth2/token scopes: read:self: >- Access your own user profile information, including basic account details and settings. read:chat: >- Read chat conversations, messages, and chat-related data. This includes viewing chat lists and message history. write:chat: >- Create new chats and send messages. This scope is required for any chat-related actions that modify data. read:experience: >- Exchange a fan's experience token for the resolved experience and the fan's identity, so an embedded fan-facing experience can render the right content. write:experience: >- Request that the creator publish or unpublish a fan-facing experience. The app mints a request token; the creator confirms and Fanvue performs the change. read:fan: Access fan-related data and information within the platform. read:post: Read posts, including post details, comments, likes, and tips. write:post: Create, edit, and manage posts and content on behalf of users. read:media: Access media files, images, videos, and other content assets. write:media: >- Upload, modify, and manage media files and content assets. Also required for vault folder management. read:creator: >- Access creator profiles, content, and creator-specific information. write:creator: Modify creator profiles, settings, and creator-specific data. read:insights: >- Access analytics, metrics, and insights data for performance tracking. read:tracking_links: >- Read tracking links and the users associated with them, including per-user tracking metadata. write:tracking_links: Create and delete tracking links. read:agency: Read agency information, including the agency's team members. write:agency: >- Manage agency team members and invites, including inviting new team members and creators. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.