> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pnplayer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Request an expansion pack

> Submits a request for extra storage or bandwidth. Either pick a `catalogPackId` or describe a custom pack with `addedMb` and/or a `note`. The request is created with status `requested` and activated by PN Player. Requires the `READ_BILLING` scope.



## OpenAPI

````yaml POST /v1/api/billing/expansion-packs/request
openapi: 3.1.0
info:
  title: PN Player API
  description: >-
    Manage videos, captions, playlists, tags, analytics, team members and
    account settings for your PN Player account.


    All `/v1/api` endpoints accept either an API key in the `X-Auth-Token`
    header or a JWT in the `Authorization: Bearer` header. Most endpoints also
    require the calling user to hold a specific role (scope): `READ_MEDIA`,
    `UPDATE_MEDIA`, `READ_ANALYTICS`, `READ_BILLING`, `READ_SETTINGS`,
    `UPDATE_SETTINGS` or `UPDATE_USERS`. The required scope is noted on each
    endpoint.
  version: 2.0.0
servers:
  - url: https://api.pnplayer.com
security:
  - apiKeyAuth: []
  - bearerAuth: []
tags:
  - name: Authentication
    description: >-
      Obtain a session token or reset a password. These endpoints do not require
      authentication.
  - name: Videos
    description: Create, list, update and delete videos.
  - name: Captions
    description: Upload, download, transcribe and manage caption tracks for a video.
  - name: Playlists
    description: Manual and rule-based (dynamic) playlists.
  - name: Tags
    description: Account-level tags that can be attached to videos.
  - name: Analytics
    description: Playback, engagement and usage metrics.
  - name: Reports
    description: Saved analytics report links.
  - name: Account
    description: Team members and account-wide streaming and security settings.
  - name: Profile
    description: The authenticated user's own profile.
  - name: API keys
    description: Long-lived keys for programmatic access.
  - name: Webhooks
    description: Configure the HTTPS endpoint that receives signed event notifications.
  - name: Billing
    description: Plan, usage, invoices, expansion packs and billing address.
  - name: Transcription settings
    description: Per-account key/value settings for automatic transcription.
  - name: Feature requests
    description: Submit, upvote and discuss feature requests.
  - name: Agreements
    description: Data processing agreement (DPA) and enterprise order form signing.
paths:
  /v1/api/billing/expansion-packs/request:
    post:
      tags:
        - Billing
      summary: Request an expansion pack
      description: >-
        Submits a request for extra storage or bandwidth. Either pick a
        `catalogPackId` or describe a custom pack with `addedMb` and/or a
        `note`. The request is created with status `requested` and activated by
        PN Player. Requires the `READ_BILLING` scope.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - type
              properties:
                type:
                  type: string
                  enum:
                    - storage
                    - bandwidth
                catalogPackId:
                  type: integer
                  description: >-
                    ID from the catalog. Name, size and price are taken from the
                    catalog entry.
                addedMb:
                  type: integer
                  minimum: 1
                  description: Custom size in MB (ignored when `catalogPackId` is given)
                note:
                  type: string
                  description: Free-text note for a custom request
      responses:
        '201':
          description: Request created
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    $ref: '#/components/schemas/AccountExpansionPack'
        '400':
          description: Validation error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ValidationError'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          description: No active billing record or catalog pack not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    AccountExpansionPack:
      type: object
      properties:
        id:
          type: integer
        accountId:
          type: string
        billingId:
          type: integer
        catalogPackId:
          type: integer
          nullable: true
          description: '`null` for custom packs'
        name:
          type: string
        type:
          type: string
          enum:
            - storage
            - bandwidth
        addedMb:
          type: integer
        priceCents:
          type: integer
        currency:
          type: string
        status:
          type: string
          enum:
            - requested
            - active
            - canceled
            - expired
        startDate:
          type: string
          format: date
        endDate:
          type: string
          format: date
        note:
          type: string
          nullable: true
        createdAt:
          type: string
          format: date-time
    ValidationError:
      type: object
      properties:
        message:
          type: string
        errors:
          type: object
          description: Field-level validation errors
          additionalProperties: true
    Error:
      type: object
      required:
        - message
      properties:
        message:
          type: string
  responses:
    Forbidden:
      description: The caller lacks the required scope
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            message: Forbidden
  securitySchemes:
    apiKeyAuth:
      type: apiKey
      in: header
      name: X-Auth-Token
      description: >-
        API key created in the dashboard or via `POST /v1/api/api-keys`. Keys
        are prefixed `pn_` and do not expire until revoked.
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Session token from `POST /auth/token`, valid for 24 hours.

````