> ## Documentation Index > Fetch the complete documentation index at: https://docs.arcuserp.com/llms.txt > Use this file to discover all available pages before exploring further. # Record a manual freight quote > Records a freight quote the operator obtained outside Shippo, by phone or through a carrier portal, requiring a carrier and amount and defaulting currency to USD. The order must already be flagged as freight, and the new quote starts unaccepted until a separate accept call is made; requires `orders:write` scope. ## OpenAPI ````yaml /openapi.yaml post /freight_orders/{id}/quotes openapi: 3.1.0 info: title: Arcus ERP Public API version: 1.0.0 description: > Arcus ERP public REST API. Designed for external integrations and data migration. **Authentication.** Bearer token (API key) via the `Authorization` header. Format: `Authorization: Bearer ark_live_ent__` (or `ark_test_*` for sandbox). API keys are issued per-entity in **Settings > Developers > API Keys**. **Entity scoping.** The entity is encoded in the API key prefix; routes are flat (e.g. `/v1/accounts`, `/v1/orders`, `/v1/products`). A small set of platform endpoints (migration, reconciliation, events, webhook endpoints, API keys) use the `/v1/entities/{entity_id}/...` form -- those are noted in their tags. **Key capabilities.** - Related-resource hydration via `?expand[]=` (see `x-arcus-expand` on each resource). - Cursor-based pagination (`starting_after` / `ending_before` / `limit`). - Idempotency via the `Idempotency-Key` header. - Webhook events for asynchronous notification. - Conditional requests / ETag for cache validation. **Changelog.** Entries are dated and name every published contract whose MEANING moved, not only the ones whose field names changed. The narrative version of the same entries, written for integrators, is published at https://arcuserp.mintlify.app/changelog. **2026-09-22 (planned 2026-09-21), REORDER-BUYER-TRUTH: demand changed what it MEANS on three published contracts, with no field renamed.** An integrator that pins field names sees no breakage and different numbers, which is why this entry exists. - **Demand now counts build consumption.** `demand_avg_per_day` on the public product, kit and inventory-balance objects, and `daily_demand` / `demand_basis` / `net_suggested_qty` on `GET /v1/purchasing/reorder-report`, are composed from fulfilled sales lines PLUS posted `build_consume` inventory draws: each physical decrement of a product counts exactly once. The previous rule adopted an internal-consumption basis only when the sales blend was exactly zero, so a product both sold AND consumed into work orders planned as if the build draws did not exist. Products drawn into work orders move; on one production-shaped dataset five did, the largest from 0.05/day to 14.95/day. - **`demand_basis` now carries four values, not two:** `sales`, `sales_and_builds`, `builds` and `consumption`. A consumer with a two-branch reader (anything that is not `consumption` is `sales`) silently hides the two new ones. - **`current_demand_units` on `GET /v1/inventory/balances/:id` moved, by a second rule.** It counts committed-but-unshipped CUSTOMER demand, and it now counts a kit component's own line rather than its parent kit line, and excludes non-sales documents. On one production dataset 269 of 1,043 balance rows changed, 227 of them downward; the largest single move was 1,941 to 25, on a product whose open PURCHASE order line had been reported as customer demand. Re-baseline anything that alerts or reorders off this field. - `run_rate_30/90/180/365` and `blended_daily` on the same balance object move for the first reason above. - **Added, not changed:** `GET /v1/purchasing/reorder-report` accepts `demand_window` and returns the unit, cover-through and reorder-point-provenance fields documented on that operation; `order_multiple` is accepted and returned on the product-vendor doors. - **Volume note.** The `inventory.low_stock`, `inventory.out_of_stock` and `inventory.back_in_stock` webhook events are population-gated on `on_hand <= reorder_point`, and reorder points move with the demand above, so subscribers should expect a one-time step change in event volume around the release. servers: - url: https://api.arcuserp.com/v1 description: Arcus ERP API (accepts both live `ark_live_*` and test `ark_test_*` keys) - url: https://dev-api.arcuserp.com/v1 description: >- Dev sandbox API (test-only data, accepts `ark_test_*` keys against dev RDS) security: [] paths: /freight_orders/{id}/quotes: parameters: - name: id in: path required: true schema: type: string format: uuid post: tags: - Freight summary: Record a manual freight quote description: >- Records a freight quote the operator obtained outside Shippo, by phone or through a carrier portal, requiring a carrier and amount and defaulting currency to USD. The order must already be flagged as freight, and the new quote starts unaccepted until a separate accept call is made; requires `orders:write` scope. operationId: createFreightQuoteV1 parameters: - $ref: '#/components/parameters/IdempotencyKey' requestBody: required: true content: application/json: schema: type: object required: - carrier_name - amount properties: carrier_name: type: string maxLength: 100 example: Estes Express carrier_service: type: string maxLength: 60 nullable: true example: Standard LTL quote_number: type: string maxLength: 80 nullable: true example: EST-2026-77821 transit_days: type: integer minimum: 0 nullable: true example: 4 amount: type: number format: float minimum: 0 example: 642.5 currency: type: string default: USD example: USD expires_at: type: string format: date-time nullable: true example: '2026-05-25T17:00:00Z' notes: type: string nullable: true raw_response: type: object nullable: true description: Optional raw carrier payload for the audit trail. example: carrier_name: Estes Express carrier_service: Standard LTL quote_number: EST-2026-77821 transit_days: 4 amount: 642.5 currency: USD expires_at: '2026-05-25T17:00:00Z' notes: Phoned in 2026-05-18 by S. Allen. responses: '201': description: Freight quote created content: application/json: schema: type: object properties: data: $ref: '#/components/schemas/FreightQuote' '400': description: order_not_freight, failed_to_create_quote, or validation error content: application/json: schema: $ref: '#/components/schemas/Error' '401': $ref: '#/components/responses/Error' '403': $ref: '#/components/responses/Error' '404': $ref: '#/components/responses/Error' security: - ApiKeyAuth: - orders:write components: parameters: IdempotencyKey: name: Idempotency-Key in: header required: false description: | Client-generated unique key for idempotent POST/PATCH/DELETE operations. Alias for the Idempotency parameter. Max 255 chars. On retry with the same key, the original response is returned without re-executing the operation. Keys expire after 24 hours. schema: type: string maxLength: 255 schemas: FreightQuote: type: object description: > A carrier rate-quote attached to a freight order. Created either manually (operator booked a carrier outside Shippo) via POST /freight_orders/{id}/quotes, or in bulk by pulling Shippo LTL rates via POST /freight_orders/{id}/quotes/shippo. Exactly one quote per order may carry a non-null `accepted_at`; accepting a quote rolls its `amount` into `orders.shipping_total`. Rule 23 SSOT: `amount` is written only by createFreightQuoteHandler and the Shippo rate-import; `accepted_at` is written only by acceptFreightQuoteHandler. Scope: orders:read / orders:write. properties: id: type: string format: uuid readOnly: true entity_id: type: string format: uuid readOnly: true order_id: type: string format: uuid carrier_name: type: string description: Carrier label (Estes, ODFL, R+L, SAIA, etc.). 1..100 chars. carrier_service: type: string nullable: true description: Service level (Standard LTL, Guaranteed, Volume, etc.). quote_number: type: string nullable: true description: Carrier-issued quote/PRO reference, when available. transit_days: type: integer nullable: true description: Estimated transit in business days. amount: type: number format: float description: Quoted freight cost (USD by default; see currency). currency: type: string default: USD example: USD quoted_at: type: string format: date-time readOnly: true expires_at: type: string format: date-time nullable: true description: Carrier quote validity expiry. accepted_at: type: string format: date-time nullable: true readOnly: true description: Non-null on the one accepted quote per order. accepted_by_id: type: string format: uuid nullable: true readOnly: true notes: type: string nullable: true raw_response: type: object nullable: true description: >- Original carrier rate payload (Shippo response object when sourced from Shippo). created_by_id: type: string format: uuid nullable: true readOnly: true created_at: type: string format: date-time readOnly: true updated_at: type: string format: date-time readOnly: true metadata: type: object description: Free-form caller metadata. Default {}. Error: description: | Alias for ErrorEnvelope. Canonical error response shape used by all API endpoints. Refer to ErrorEnvelope for the full field definition. allOf: - $ref: '#/components/schemas/ErrorEnvelope' ErrorEnvelope: type: object description: | Canonical error response envelope. All API errors use this shape. required: - error - code properties: error: type: string description: Machine-readable error key example: not_found code: type: string description: Machine-readable error code (often same as error) example: not_found type: type: string enum: - validation_error - permission_error - not_found - conflict - rate_limit - internal - expand_error - not_implemented example: not_found hint: type: string description: Human-readable one-sentence explanation (English) example: >- The requested order does not exist or does not belong to this entity. param: type: string description: The parameter that caused the error, if applicable example: expand[0] required: type: string description: The scope required (only on insufficient_scope errors) example: accounts:read request_id: type: string description: >- Unique request ID for support tracing (maps to CloudWatch log stream) example: req_abc123 responses: Error: description: Error response (400/401/403/404/409/422/429/500) content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' securitySchemes: ApiKeyAuth: type: http scheme: bearer description: | API key issued per entity via Settings > Developers > API Keys. Each key carries scopes (e.g. orders:read, products:write). Bearer token format: Authorization: Bearer ark_live_ent__ Test keys use ark_test_ent__. Both are issued per entity via Settings > Developers > API Keys. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.