> ## 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. # List supplier acceptance responses > Get a paginated list of a supplier's responses to a purchase order, made through the supplier portal. Newest first. The underlying table is append-only — a supplier who changes their mind adds a new row — so **the first row is the current state**. A purchase order with no acceptance rows is **pending**; that value is never stored. > **A proposal never changes the purchase order.** The `proposed_qty`, > `proposed_unit_price` and `proposed_ship_date` fields on each line record > what the supplier asked for. The PO keeps its original values until someone > on the buying side applies the change deliberately. Do not read a proposal > as an agreed term. There is deliberately no endpoint for creating an acceptance: an acceptance is the supplier's own statement, made through the portal, and recording one on their behalf would turn the audit trail into a record of what the buyer wished they had said. This API reads what the supplier said. ## OpenAPI ````yaml /api-reference/build.yaml get /purchase-orders/{purchaseOrderId}/supplier-acceptances 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: /purchase-orders/{purchaseOrderId}/supplier-acceptances: get: tags: - Supplier Portal summary: List supplier acceptance responses description: > Get a paginated list of a supplier's responses to a purchase order, made through the supplier portal. Newest first. The underlying table is append-only — a supplier who changes their mind adds a new row — so **the first row is the current state**. A purchase order with no acceptance rows is **pending**; that value is never stored. > **A proposal never changes the purchase order.** The `proposed_qty`, > `proposed_unit_price` and `proposed_ship_date` fields on each line record > what the supplier asked for. The PO keeps its original values until someone > on the buying side applies the change deliberately. Do not read a proposal > as an agreed term. There is deliberately no endpoint for creating an acceptance: an acceptance is the supplier's own statement, made through the portal, and recording one on their behalf would turn the audit trail into a record of what the buyer wished they had said. This API reads what the supplier said. operationId: getSupplierAcceptances parameters: - in: path name: purchaseOrderId required: true schema: type: integer description: Purchase order ID - in: query name: page schema: type: integer default: 1 description: Page number for pagination - in: query name: per_page schema: type: integer default: 10 maximum: 100 description: Number of items per page (max 100) responses: '200': description: Paginated acceptance responses, newest first content: application/json: schema: type: object properties: data: type: array items: type: object description: > A supplier's response to a purchase order, made through the supplier portal. The underlying table is append-only — a supplier who changes their mind adds a new row — so within the newest-first list the first row is the current state. A purchase order with no acceptance rows is **pending**; that value is never stored. properties: id: type: integer example: 1 purchase_order_id: type: integer example: 7 status: type: string enum: - accepted - accepted_with_changes - rejected description: > The header-level outcome. `pending` is never stored — a purchase order with no acceptance row is pending. example: accepted_with_changes responded_at: type: string format: date-time example: '2026-08-28T15:13:13.000000Z' note: type: string nullable: true example: Can ship 180 by the requested date. contact_details_id: type: integer nullable: true description: The supplier contact who responded, when known. example: 1 created_at: type: string format: date-time example: '2026-08-28T15:13:13.000000Z' updated_at: type: string format: date-time example: '2026-08-28T15:13:13.000000Z' lines: type: array items: type: object description: > A supplier's response to one purchase order line. The `proposed_*` values are a request, not an agreed term — the purchase order keeps its original values until someone on the buying side applies the change deliberately. properties: id: type: integer example: 1 purchase_order_item_id: type: integer example: 15 status: type: string enum: - accepted - changes_proposed - rejected example: changes_proposed proposed_qty: type: string nullable: true description: > Quantity the supplier proposed for this line. `null` means no change was proposed on this dimension, which is NOT the same as proposing zero (a supplier proposing zero sends `"0"`). Branch on `null`, not on falsiness. example: '180.000000' proposed_unit_price: type: string nullable: true description: >- Proposed unit price. `null` means no change proposed. See `proposed_qty`. example: null proposed_ship_date: type: string format: date nullable: true description: >- Proposed ship date (YYYY-MM-DD). `null` means no change proposed. See `proposed_qty`. example: '2026-09-15' note: type: string nullable: true example: Short on materials meta: type: object properties: current_page: type: integer description: The current page number example: 1 from: type: integer description: The starting index of the paginated results example: 1 last_page: type: integer description: The last page number example: 5 per_page: type: integer description: Number of items per page example: 10 to: type: integer description: The ending index of the paginated results example: 10 total: type: integer description: Total number of items across all pages example: 50 '401': description: Unauthorized content: application/json: schema: type: object properties: message: type: string '404': description: Purchase order not found 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. ````