> ## 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 multipart upload session > Create a media record and start an S3 multipart upload session. **Required scope** * `write:media` — Upload, modify, and manage media files and content assets. Also required for vault folder management. ## OpenAPI ````yaml /openapi.json post /media/uploads openapi: 3.1.0 info: title: Fanvue API version: '0.1' servers: [] security: [] paths: /media/uploads: post: summary: Create multipart upload session description: Create a media record and start an S3 multipart upload session. operationId: createUploadSession parameters: - $ref: '#/components/parameters/ApiVersionHeader' requestBody: required: true content: application/json: schema: type: object properties: name: type: string minLength: 1 maxLength: 255 filename: type: string minLength: 1 maxLength: 255 mediaType: type: string enum: - image - video - audio - document sizeBytes: type: integer exclusiveMinimum: 0 maximum: 1610612736 description: >- Total size of the file in bytes. When provided, the response includes the exact `totalParts` to upload. required: - name - filename - mediaType responses: '200': description: Upload session created content: application/json: schema: type: object properties: mediaUuid: type: string format: uuid uploadId: type: string partSize: type: integer description: >- Size in bytes of every part except the final one (which may be smaller). maxParts: type: integer description: >- Maximum number of parts allowed, derived from the maximum supported file size. totalParts: type: - integer - 'null' description: >- Exact number of parts to upload, computed from `sizeBytes`. Null when `sizeBytes` was not provided — compute it client-side as ceil(fileSize / partSize). required: - mediaUuid - uploadId - partSize - maxParts - totalParts example: mediaUuid: d4e5f6a7-8b9c-0d1e-2f3a-4b5c6d7e8f9a uploadId: abc123XYZ789multipart partSize: 6291456 maxParts: 854 totalParts: 4 '400': description: Bad Request - API version not supported OR validation failed content: application/json: schema: oneOf: - $ref: '#/components/schemas/UnsupportedVersionError' - $ref: '#/components/schemas/ValidationError' '401': $ref: '#/components/responses/UnauthorizedResponse' '403': $ref: '#/components/responses/UnauthorizedResponse' '410': $ref: '#/components/responses/SunsetVersionResponse' '429': $ref: '#/components/responses/RateLimitResponse' security: - BearerAuth: - write:media 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 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. ````