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

# Submit Flight Manifest

> Submit flight manifest with FFM/XFFM data

Submit flight manifest with FFM/XFFM data.

<ParamField status="201" type="FlightManifestResponse">
  <ParamField name="manifestId" type="string">
    Manifest ID
  </ParamField>

  <ParamField name="flightId" type="string">
    Flight ID
  </ParamField>

  <ParamField name="status" type="string">
    Submission status
  </ParamField>
</ParamField>

### Reference Documentation

<Info>
  For more information on flight manifest creation with FFM, please refer to:

  * Pages 221-222 of "Functional\_Requirements\_V18 FINAL": [https://belli.sg/4nxxCDR](https://belli.sg/4nxxCDR)
</Info>


## OpenAPI

````yaml POST /api/flights/{id}/manifests
openapi: 3.0.3
info:
  title: Mock API
  version: 1.0.0
  description: >-
    Mock OpenAPI spec for QR API Service. All endpoints require API key
    authentication via 'Authorization: Bearer <token>' or 'x-api-key: <token>'
    headers.
servers:
  - url: https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io
    description: Production server
security:
  - ApiKeyAuth: []
  - ApiKeyHeader: []
tags:
  - name: auth-v1
    description: Authentication and user management
  - name: reference-data-v1
    description: Reference data and master data
  - name: flights-v1
    description: Flight schedules and capacity
  - name: quotes-v1
    description: Quotation and pricing
  - name: awb-stock-v1
    description: AWB Stock Management
  - name: bookings-v1
    description: Booking management
  - name: shipments-v1
    description: Shipment documents and tracking
  - name: compliance-v1
    description: Compliance and safety declarations
  - name: operations-v1
    description: Operational events and manifests
  - name: webhooks-v1
    description: Webhook management
  - name: admin-v1
    description: Administrative and audit functions
  - name: qr-exp-cgo-ext-availability-v1
    description: Legacy availability service
  - name: qr-exp-cgo-ext-booking-v1
    description: Legacy booking service
  - name: qr-exp-cgo-ext-flight-schedules-v1
    description: Legacy flight schedules service
  - name: qr-exp-cgo-shipments-v1
    description: Legacy shipments service
  - name: qr-exp-cgo-stock-v1
    description: Legacy stock service
  - name: qr-exp-cgo-tables-v1
    description: Legacy table data service
paths:
  /api/flights/{id}/manifests:
    post:
      tags:
        - operations-v1
      summary: Submit flight manifest
      description: Submit flight manifest with FFM/XFFM data
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
          description: Flight ID
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/FlightManifestRequest'
      responses:
        '201':
          description: Manifest submitted
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/FlightManifestResponse'
components:
  schemas:
    FlightManifestRequest:
      type: object
      properties:
        flightId:
          type: string
          example: QR001-20240101
        awbNumbers:
          type: array
          items:
            type: string
          example:
            - '15712345678'
            - '15712345679'
        totalPieces:
          type: integer
          example: 20
        totalWeight:
          type: number
          example: 1000
        totalVolume:
          type: number
          example: 15
      required:
        - flightId
        - awbNumbers
        - totalPieces
        - totalWeight
    FlightManifestResponse:
      type: object
      properties:
        manifestId:
          type: string
          example: manifest-123
        flightId:
          type: string
          example: QR001-20240101
        status:
          type: string
          example: submitted
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
    ApiKeyHeader:
      type: apiKey
      in: header
      name: x-api-key

````