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

# Preview fulfillment-order push mapping

> Fulfillment-order-scoped mapping preview. Resolves the PUSH_ORDERS integration mapping
from the fulfillment order's fulfillment channel and renders the output that *would* be
sent to the destination OMS — without pushing.

Optionally send an unsaved `mapping_config` draft to preview changes before saving them.
Useful for diagnosing why a push is producing empty or invalid fields.




## OpenAPI

````yaml /api-reference/build.yaml post /fulfillment-orders/{fulfillmentOrderId}/push-preview
openapi: 3.0.0
info:
  title: Luminous API
  version: 1.0.0
  description: API documentation for Luminous
servers:
  - url: https://{companyName}.api.joinluminous.com/external/api/v1
    variables:
      companyName:
        default: companyName
        description: Your company-specific subdomain
security: []
tags:
  - name: Products
    description: Get and manage products
  - name: Pricing
    description: Manage price schedules, levels, and customizations
  - name: BOMs
    description: Manage Bills of Materials (BOMs)
  - name: Labels
    description: Label rendering via Labelary ZPL service
  - name: Companies
    description: Manage business accounts and their associated data
  - name: Contacts
    description: Manage contact information for individuals
  - name: Suppliers
    description: Manage suppliers (factories) — vendors used on purchase orders
  - name: Supplier SKUs
    description: Manage per-supplier SKU and unit-cost overrides for products
  - name: Locations
    description: Manage warehouses and locations
  - name: Inventory
    description: Get and adjust product stock levels
  - name: Lots
    description: Create, update, and delete product lots (batches)
  - name: Transfer Orders
    description: Manage transfer orders
  - name: Fulfillment Orders
    description: Manage fulfillment orders and picklists
  - name: Fulfillment Priority Lists
    description: Configure fulfillment routing priority lists
  - name: Purchase Orders
    description: Get and modify purchase orders
  - name: Supplier Portal
    description: >-
      Read a supplier's response to a purchase order and control the one-click
      portal link
  - name: Receiving Reports
    description: Manage receiving reports
  - name: Payment Obligations
    description: Manage payment obligations for purchase orders
  - name: Sales Orders
    description: Manage sales orders and sales order shipments
  - name: Purgatory
    description: >-
      Inspect and resolve non-posted sales orders in the purgatory staging
      workflow
  - name: PickFlow Shipping
    description: >-
      Provider-agnostic shipping rates, services, packages, and label purchase
      for PickFlow
  - name: Cycle Counts
    description: >-
      Create, drive, and post PickFlow cycle counts — batches, per-warehouse
      sessions, and CSV import/export
  - name: Print Stations
    description: List paired print stations and enqueue print jobs to them
  - name: Invoices
    description: Get and manage invoices
  - name: Work Orders
    description: >-
      Manage work orders — production lifecycle, steps, materials, links,
      shipments, and comments
  - name: Production Batches
    description: Group and manage work orders as production batches
  - name: Bills
    description: >-
      Accounts payable bill management, payments, attachments, allocations, and
      variance
  - name: Prepayments
    description: Manage vendor prepayments and applications
  - name: Vendor Credits
    description: Manage vendor credits and applications
  - name: Vendor Returns
    description: Manage vendor returns and credit generation
  - name: Customer Returns
    description: Manage customer returns (sales returns), receiving, and restock behavior
  - name: Stock Snapshot
    description: Point-in-time stock snapshots with export support
  - name: Consumption
    description: Consumption reports and exports
  - name: Inventory Aging
    description: Cost-layer-based inventory aging reports
  - name: Bills Reports
    description: Accounts payable bills aging reports
  - name: Forecast
    description: Materialized forecast data
  - name: Reports
    description: Close the books, inventory discrepancy, transaction COGS, and EDI reports
  - name: Tags
    description: Add/remove tags across various resources
  - name: Custom Fields
    description: Get and set custom fields across various resources
  - name: Currency
    description: Currency configuration, exchange rates, and conversion
  - name: Integration Mappings
    description: Manage integration mappings for external systems
  - name: Integration Field Mappings
    description: Manage field-level mappings between Luminous and external systems
paths:
  /fulfillment-orders/{fulfillmentOrderId}/push-preview:
    post:
      tags:
        - Fulfillment Orders
      summary: Preview fulfillment-order push mapping
      description: >
        Fulfillment-order-scoped mapping preview. Resolves the PUSH_ORDERS
        integration mapping

        from the fulfillment order's fulfillment channel and renders the output
        that *would* be

        sent to the destination OMS — without pushing.


        Optionally send an unsaved `mapping_config` draft to preview changes
        before saving them.

        Useful for diagnosing why a push is producing empty or invalid fields.
      operationId: previewFulfillmentOrderPush
      parameters:
        - in: path
          name: fulfillmentOrderId
          required: true
          schema:
            type: integer
          description: ID of the fulfillment order
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
              properties:
                mapping_config:
                  type: array
                  description: >
                    Optional unsaved draft mapping to preview instead of the
                    saved mapping.

                    Each entry must include a `pushField`.
                  items:
                    type: object
                    required:
                      - pushField
                    properties:
                      pushField:
                        type: string
                    additionalProperties: true
      responses:
        '200':
          description: Mapping preview
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: object
                    properties:
                      mapping_id:
                        type: integer
                        description: The resolved PUSH_ORDERS integration mapping id.
                      output:
                        description: The rendered mapping output that would be pushed.
                        additionalProperties: true
                      rows:
                        type: array
                        description: >-
                          Per-field mapping rows with resolved values and
                          status.
                        items:
                          type: object
                          additionalProperties: true
                      summary:
                        type: object
                        additionalProperties: true
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
        '422':
          description: >
            The fulfillment channel has no PUSH_ORDERS integration mapping
            attached, or the

            provided `mapping_config` is invalid.
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
      security:
        - BearerAuth: []
components:
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: >-
        Authenticate using a bearer token. To create a token, navigate to
        /settings/api-tokens and click Create API Token.

````