> ## 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. # Push fulfillment order to OMS > Push this fulfillment order to its destination OMS (fulfillment channel). The destination is determined by the fulfillment order's existing channel mapping; no destination is taken from the request body. Optionally enable per-request HTTP debug capture by sending `{ "debug": true }` — the debug payload is returned inline alongside the result. Same behavior as the admin bulk push action. ## OpenAPI ````yaml /api-reference/build.yaml post /fulfillment-orders/{id}/push 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: Purchase Orders description: Get and modify purchase orders - 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/{id}/push: post: tags: - Fulfillment Orders summary: Push fulfillment order to OMS description: > Push this fulfillment order to its destination OMS (fulfillment channel). The destination is determined by the fulfillment order's existing channel mapping; no destination is taken from the request body. Optionally enable per-request HTTP debug capture by sending `{ "debug": true }` — the debug payload is returned inline alongside the result. Same behavior as the admin bulk push action. operationId: pushFulfillmentOrder parameters: - in: path name: id required: true schema: type: integer description: ID of the fulfillment order requestBody: required: false content: application/json: schema: type: object properties: debug: type: boolean description: >- When true, capture and return outbound OMS HTTP traffic in `data.debug`. default: false responses: '200': description: Push succeeded content: application/json: schema: type: object properties: data: type: object properties: success: type: boolean message: type: string data: type: object description: >- Provider-specific response payload (only present when the OMS returned data). additionalProperties: true debug: type: object description: >- Present only when `debug=true` was sent in the request body. additionalProperties: true '401': description: Unauthorized content: application/json: schema: type: object properties: message: type: string '404': description: Fulfillment order not found content: application/json: schema: type: object properties: message: type: string '422': description: > Push failed (validation error or OMS rejected the push). When the failure is due to a duplicate-push / desync state, the response includes a `data.links.reconcile` URL pointing to the reconcile-source-reference endpoint for this fulfillment order. content: application/json: schema: type: object properties: data: type: object properties: success: type: boolean example: false message: type: string data: type: object additionalProperties: true links: type: object description: >- Present when the failure can be resolved by reconciling the source reference. properties: reconcile: type: string description: >- URL to POST to in order to reconcile the source reference. docs: type: string description: Documentation URL for the reconcile endpoint. debug: type: object additionalProperties: true 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. ````