> ## 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. # Get app pricing subscription lifecycle status > Returns pricing plan lifecycle states for a developer-owned app (`pending_setup`, `active`, `withdrawn`). **Required scope** * `read:self` — Access your own user profile information, including basic account details and settings. ## OpenAPI ````yaml /openapi.json get /apps/{appUuid}/subscription-status openapi: 3.1.0 info: title: Fanvue API version: '0.1' servers: [] security: [] paths: /apps/{appUuid}/subscription-status: get: summary: Get app pricing subscription lifecycle status description: >- Returns pricing plan lifecycle states for a developer-owned app (`pending_setup`, `active`, `withdrawn`). operationId: getAppSubscriptionStatus parameters: - $ref: '#/components/parameters/ApiVersionHeader' - schema: type: string format: uuid example: 00000000-0000-4000-8000-000000000001 required: true name: appUuid in: path responses: '200': description: Pricing plan lifecycle summary for the app content: application/json: schema: type: object properties: appUuid: type: string format: uuid appName: type: string availability: type: string enum: - complete - horizonUnavailable overallStatus: type: string enum: - notConfigured - pendingSetup - active - withdrawn - mixed - unavailable pricingPlans: type: array items: type: object properties: uuid: type: string format: uuid name: type: string billingType: type: string enum: - free - one_time - recurring interval: type: - string - 'null' enum: - monthly - yearly price: type: number currencyCode: type: string status: type: string enum: - pending_setup - active - withdrawn checkoutUrl: type: - string - 'null' format: uri required: - uuid - name - billingType - interval - price - currencyCode - status - checkoutUrl required: - appUuid - appName - availability - overallStatus - pricingPlans example: appUuid: 00000000-0000-4000-8000-000000000001 appName: Example App availability: complete overallStatus: pendingSetup pricingPlans: - uuid: 00000000-0000-4000-8000-000000000002 name: Monthly billingType: recurring interval: monthly price: 999 currencyCode: USD status: pending_setup checkoutUrl: null - uuid: 00000000-0000-4000-8000-000000000005 name: Yearly billingType: recurring interval: yearly price: 9990 currencyCode: USD status: active checkoutUrl: https://www.fanvue.com/checkout/app_000000001VgEh72lXvTXkL '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: App not found or not owned by the authenticated user content: application/json: schema: type: object properties: message: type: string '410': $ref: '#/components/responses/SunsetVersionResponse' '429': $ref: '#/components/responses/RateLimitResponse' '502': description: Failed to load subscription status from 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:self 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. ````