> ## 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. # Update subscription price > Set the authenticated creator's monthly subscription price, in USD cents (minor units). **⚠️ Side effect when increasing the price:** all existing active subscribers are moved to a pending opt-in state for the new price. With `forceOptIn: false` (default) they keep auto-renewing at their current price until they accept the new one; with `forceOptIn: true` they are forced to opt in at the new price and their current auto-renewal is disabled. The response's `subscribersMovedToReOptIn` reports whether this happened. Decreasing the price has no effect on existing subscribers. The new price must stay compatible with the creator's promotions: if any promotion's discount would take it below the platform minimum, the request is rejected until that promotion is deleted. **Required scope** * `write:creator` — Modify creator profiles, settings, and creator-specific data. ## OpenAPI ````yaml /openapi.json patch /users/me/subscription-price openapi: 3.1.0 info: title: Fanvue API version: '0.1' servers: [] security: [] paths: /users/me/subscription-price: patch: summary: Update subscription price description: >- Set the authenticated creator's monthly subscription price, in USD cents (minor units). **⚠️ Side effect when increasing the price:** all existing active subscribers are moved to a pending opt-in state for the new price. With `forceOptIn: false` (default) they keep auto-renewing at their current price until they accept the new one; with `forceOptIn: true` they are forced to opt in at the new price and their current auto-renewal is disabled. The response's `subscribersMovedToReOptIn` reports whether this happened. Decreasing the price has no effect on existing subscribers. The new price must stay compatible with the creator's promotions: if any promotion's discount would take it below the platform minimum, the request is rejected until that promotion is deleted. operationId: updateSubscriptionPrice parameters: - $ref: '#/components/parameters/ApiVersionHeader' requestBody: content: application/json: schema: type: object properties: subscriptionPrice: type: integer minimum: 399 maximum: 10000 description: >- New monthly subscription price in USD cents (minor units), between 399 and 10000 forceOptIn: type: boolean default: false description: >- Only used when the price increases. When false (default), existing subscribers keep auto-renewing at their current price until they opt in to the new one. When true, they are forced to opt in at the new price and their current auto-renewal is disabled. required: - subscriptionPrice responses: '200': description: Subscription price updated successfully content: application/json: schema: type: object properties: subscriptionPrice: type: integer description: >- The subscription price now in effect, in USD cents (minor units) subscribersMovedToReOptIn: type: boolean description: >- True when the price increase moved existing active subscribers to a pending re-opt-in state (see the endpoint description) required: - subscriptionPrice - subscribersMovedToReOptIn example: subscriptionPrice: 999 subscribersMovedToReOptIn: true '400': description: >- Invalid price, not a creator account, or conflicting active promotion content: application/json: schema: type: object properties: message: type: string required: - message '401': $ref: '#/components/responses/UnauthorizedResponse' '403': $ref: '#/components/responses/UnauthorizedResponse' '410': $ref: '#/components/responses/SunsetVersionResponse' '429': $ref: '#/components/responses/RateLimitResponse' security: - BearerAuth: - write:creator 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 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. ````