> ## 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. # List inventory transfers (warehouse, intercompany, FBA inbound) > Returns a paginated list of inventory transfer records for the entity. A transfer is visible when EITHER endpoint matches the active location (Pattern A on `inventory_transfers.location_from_id` OR `location_to_id`), mirroring the bin-movements operator mental model "show me every transfer that touches LOC-X". Layer 4 location isolation (NEW-GAP-API-V1-LIST-X-LOCATION-ID-SWEEP, 2026-05-17): the wrapper applies the `X-Location-Id` request header first, then the `location_id` query param (header takes precedence). When neither is set, the response is entity-wide (admin view). `location_from_id` and `location_to_id` are NOT NULL in the schema, so there is no NULL-universal carve-out for transfers. Filter set: `status`, `transfer_type`, `search` (transfer_number prefix + trigram similarity). The page also returns a `stats` object with rollups for `active`, `pending_approval`, `in_transit`, and `closed_today` counts scoped to the same location filter. Requires `inventory:read` scope. ## OpenAPI ````yaml /openapi.yaml get /transfers 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. 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: /transfers: get: tags: - Inventory summary: List inventory transfers (warehouse, intercompany, FBA inbound) description: > Returns a paginated list of inventory transfer records for the entity. A transfer is visible when EITHER endpoint matches the active location (Pattern A on `inventory_transfers.location_from_id` OR `location_to_id`), mirroring the bin-movements operator mental model "show me every transfer that touches LOC-X". Layer 4 location isolation (NEW-GAP-API-V1-LIST-X-LOCATION-ID-SWEEP, 2026-05-17): the wrapper applies the `X-Location-Id` request header first, then the `location_id` query param (header takes precedence). When neither is set, the response is entity-wide (admin view). `location_from_id` and `location_to_id` are NOT NULL in the schema, so there is no NULL-universal carve-out for transfers. Filter set: `status`, `transfer_type`, `search` (transfer_number prefix + trigram similarity). The page also returns a `stats` object with rollups for `active`, `pending_approval`, `in_transit`, and `closed_today` counts scoped to the same location filter. Requires `inventory:read` scope. operationId: listTransfersV1 parameters: - name: X-Location-Id in: header required: false schema: type: string format: uuid description: | Active location pill (Layer 4 isolation). Takes precedence over the `location_id` query parameter. The wrapper enforces the precedence ladder header > qp > admin entity-wide, matching listOrdersV1 / listReturnsV1 / listPackagesV1 / listLabelsV1 / listSerialsV1. - name: location_id in: query schema: type: string format: uuid description: | Filter to a single warehouse location (Layer 4). Used only when `X-Location-Id` is absent. A transfer is included whenever its `location_from_id` OR `location_to_id` matches. - name: location_ids in: query schema: type: string description: | Comma-separated list of location UUIDs (multi-location restriction; user_locations gate). When supplied, supersedes both `location_id` and `X-Location-Id`. Each transfer is included when EITHER endpoint sits in the array. - name: status in: query schema: type: string enum: - draft - submitted - pending_approval - approved - rejected - in_transit - working - shipped - receiving - received - closed - cancelled - all - name: transfer_type in: query schema: type: string enum: - internal - intercompany - fba_inbound - all - name: search in: query schema: type: string description: Transfer number prefix match plus trigram similarity (> 0.3). - name: page in: query schema: type: integer minimum: 1 default: 1 - name: per_page in: query schema: type: integer minimum: 1 maximum: 100 default: 25 responses: '200': description: Paginated transfer list with stats rollup content: application/json: schema: type: object properties: data: type: array items: type: object properties: id: type: string format: uuid entity_from_id: type: string format: uuid entity_to_id: type: string format: uuid location_from_id: type: string format: uuid location_to_id: type: string format: uuid transfer_number: type: string status: type: string transfer_type: type: string item_count: type: integer total_qty: type: number created_at: type: string format: date-time total: type: integer page: type: integer per_page: type: integer total_pages: type: integer stats: type: object properties: active: type: integer pending_approval: type: integer in_transit: type: integer closed_today: type: integer '400': $ref: '#/components/responses/Error' '401': $ref: '#/components/responses/Error' '403': $ref: '#/components/responses/Error' security: - ApiKeyAuth: [] components: responses: Error: description: Error response (400/401/403/404/409/422/429/500) content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' schemas: 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 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. ````