> ## 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. # Repair address and push fulfillment order > Harness-safe recovery action for a fulfillment order that failed to push because of address gaps (e.g. a UAE/Israel-style order missing `postal_code` or `state`). In one call it will: 1. Apply the supplied `ship_to` fields to the fulfillment order (merged onto the existing address), optionally mirroring them to the sales order. 2. Clear the `error_message` and reset an `Error` status back to `planned`. 3. Unpush the order first if it was already pushed (`pushed_at` set). 4. Push the order to its destination OMS. Cannot repair a fulfillment order in a terminal status, or one that already has a picklist. ## OpenAPI ````yaml /api-reference/build.yaml post /fulfillment-orders/{fulfillmentOrderId}/repair-and-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: 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}/repair-and-push: post: tags: - Fulfillment Orders summary: Repair address and push fulfillment order description: > Harness-safe recovery action for a fulfillment order that failed to push because of address gaps (e.g. a UAE/Israel-style order missing `postal_code` or `state`). In one call it will: 1. Apply the supplied `ship_to` fields to the fulfillment order (merged onto the existing address), optionally mirroring them to the sales order. 2. Clear the `error_message` and reset an `Error` status back to `planned`. 3. Unpush the order first if it was already pushed (`pushed_at` set). 4. Push the order to its destination OMS. Cannot repair a fulfillment order in a terminal status, or one that already has a picklist. operationId: repairAndPushFulfillmentOrder 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: ship_to: type: object description: >- Address fields to apply (snake_case). Omitted fields are left unchanged. properties: postal_code: type: string nullable: true state: type: string nullable: true city: type: string nullable: true country: type: string nullable: true street1: type: string nullable: true street2: type: string nullable: true sync_ship_to_to_sales_order: type: boolean default: false description: >- When true, also write the repaired `ship_to` to the sales order. debug: type: boolean description: >- When true, capture and return outbound OMS HTTP traffic in `data.debug`. default: false responses: '200': description: Repair and push completed content: application/json: schema: type: object properties: data: type: object properties: success: type: boolean example: true message: type: string example: Repair and push completed. repaired_fields: type: object description: >- The fields that were changed during repair (e.g. `ship_to`, `error_message`, `unpushed`). additionalProperties: true push: type: object properties: success: type: boolean message: type: string data: type: object additionalProperties: true debug: type: object description: Present only when `debug=true` was sent. additionalProperties: true '401': description: Unauthorized content: application/json: schema: type: object properties: message: type: string '422': description: > Repair or push failed — e.g. the fulfillment order is in a terminal status, has a picklist, unpush failed, or the OMS rejected the push. The `data.success` field is `false`. content: application/json: schema: type: object properties: data: type: object properties: success: type: boolean example: false message: type: string repaired_fields: 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. ````