> ## 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.

# Create a new post

> Create a new post with optional media, text, and pricing.

<Info>
  **Required scope**

  * `write:post` — Create, edit, and manage posts and content on behalf of users.
</Info>


## OpenAPI

````yaml /openapi.json post /posts
openapi: 3.1.0
info:
  title: Fanvue API
  version: '0.1'
servers: []
security: []
paths:
  /posts:
    post:
      summary: Create a new post
      description: Create a new post with optional media, text, and pricing.
      operationId: createPost
      parameters:
        - $ref: '#/components/parameters/ApiVersionHeader'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                text:
                  type: string
                  maxLength: 5000
                  description: Text content of the post
                mediaUuids:
                  type: array
                  items:
                    type: string
                    format: uuid
                  description: Array of media UUIDs to attach to the post
                mediaPreviewUuid:
                  type: string
                  format: uuid
                  description: UUID of free preview media shown before unlock
                price:
                  type: number
                  minimum: 300
                  description: Price in cents for paid posts (requires media)
                audience:
                  $ref: '#/components/schemas/PostAudience'
                publishAt:
                  type: string
                  format: date-time
                  description: Future date/time to publish the post (ISO 8601 format)
                expiresAt:
                  type: string
                  format: date-time
                  description: Date/time when the post expires (ISO 8601 format)
                collectionUuids:
                  type: array
                  items:
                    type: string
                    format: uuid
                  description: Array of content collection UUIDs to assign to the post
              required:
                - audience
      responses:
        '201':
          description: Post created successfully
          content:
            application/json:
              schema:
                type: object
                properties:
                  uuid:
                    type: string
                    format: uuid
                    description: Unique identifier of the created post
                  createdAt:
                    type: string
                    format: date-time
                    description: Date/time when the post was created (ISO 8601 format)
                  text:
                    type:
                      - string
                      - 'null'
                    description: Text content of the post
                  price:
                    type:
                      - number
                      - 'null'
                    description: Price in cents for paid posts
                  mediaPreviewUuid:
                    type:
                      - string
                      - 'null'
                    format: uuid
                    description: UUID of free preview media
                  audience:
                    $ref: '#/components/schemas/PostAudience'
                  publishAt:
                    type:
                      - string
                      - 'null'
                    format: date-time
                    description: >-
                      Future date/time when the post will be published (ISO 8601
                      format)
                  publishedAt:
                    type:
                      - string
                      - 'null'
                    format: date-time
                    description: Date/time when the post was published (ISO 8601 format)
                  expiresAt:
                    type:
                      - string
                      - 'null'
                    format: date-time
                    description: Date/time when the post expires (ISO 8601 format)
                required:
                  - uuid
                  - createdAt
                  - text
                  - price
                  - mediaPreviewUuid
                  - audience
                  - publishAt
                  - publishedAt
                  - expiresAt
              example:
                uuid: 123e4567-e89b-12d3-a456-426614174000
                createdAt: '2025-01-01T12:00:00.000Z'
                text: Check out my latest content!
                price: 999
                mediaPreviewUuid: f1e2d3c4-b5a6-4789-8123-456789abcdef
                audience: subscribers
                publishAt: null
                publishedAt: '2025-01-01T12:00:00.000Z'
                expiresAt: '2025-01-01T12:00:00.000Z'
        '400':
          $ref: '#/components/responses/ValidationErrorResponse'
        '401':
          $ref: '#/components/responses/UnauthorizedResponse'
        '403':
          $ref: '#/components/responses/UnauthorizedResponse'
        '410':
          $ref: '#/components/responses/SunsetVersionResponse'
        '429':
          $ref: '#/components/responses/RateLimitResponse'
      security:
        - BearerAuth:
            - write:post
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:
    PostAudience:
      type: string
      enum:
        - subscribers
        - followers-and-subscribers
      description: Audience that can view the post
  responses:
    ValidationErrorResponse:
      description: Request validation failed
      content:
        application/json:
          schema:
            type: object
            properties:
              errors:
                type: array
                items:
                  type: string
                description: List of validation errors
            required:
              - errors
    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.

````