---
title: "What is still on order for one variant"
method: GET
path: "/api/v1/variants/{variant_id}/incoming-pos"
tags: ["variants"]
---

# What is still on order for one variant

`GET /api/v1/variants/{variant_id}/incoming-pos`

## Request

- Base URL: `https://api.app.tightly.io`
- URL: `https://api.app.tightly.io/api/v1/variants/{variant_id}/incoming-pos`
- Auth: HTTP bearer

The open orders carrying one variant, with the quantities counted for that variant alone.

Each order carries `id`, `name`, `status` (`FullyConfirmed` or `FullyShipped`), `expected_delivery_date`, `supplier_id` and `supplier_name`, `location_id` and `location_name`, `line_items` and `deliveries` for this variant, and `ordered_quantity` and `delivered_quantity` summed over this variant's lines. An order that also carries other variants is here, but its quantities are not: what is served is this variant's share.

A variant with nothing inbound answers `purchase_orders: []`, which is the empty case and not an error.

For the whole order, with every line on it, read the purchase orders resource; for the same question across a product, read the product's incoming purchase orders.

Scope: `products:read`.

## Path parameters

- `variant_id` string, required

## Headers

- `Tightly-Version` string

## Response `200`

The open orders carrying this variant, with its own ordered and delivered quantities.

- object
  - `data` object
    - `purchase_orders` object[]: One entry per open order carrying this variant.
  - `message` object: severity, service and desc.

## Other responses

- `401`: No usable key: malformed, unknown, revoked, expired or stopped. One refusal covers all five, because telling a caller which is which maps the surface for them.
- `403`: The key may not reach this operation. `scope_missing` when the key does not hold Products; `ip_not_allowed` when the caller's address is outside the key's allowlist. `plan_excludes` when the organisation's plan does not include the public API itself, which is sold with Essentials and is asked of every key minted under that gate. A key minted before the gate existed is never refused by it, whatever the plan holds. Products is ungated, so that is the only plan reason served here.
- `404`: No variant in this organisation carries that id.
- `429`: The key has spent its allowance for this minute. 600 reads and 120 writes a minute, counted per key, refused calls included. `Retry-After` says how long to wait.
- `503`: The database is briefly out of reach, which is what a failover or a full connection pool looks like from outside. Wait the seconds `Retry-After` names and send the request again. A read is safe to repeat. A write is not, because the connection was lost in the middle of it, so read the object back before sending it a second time. Branch on the status rather than on `code`, which is `POSTGRES_UNAVAILABLE` from one of the two seams that raise this and `SERVICE_UNAVAILABLE` from the other.

---

[API](https://skmtc.dev/tightly/apis/tightly-api.md) · [All operations](https://skmtc.dev/tightly/apis/tightly-api/llms.txt) · [OpenAPI document](https://skmtc.dev/tightly/apis/tightly-api/revisions/199f7eb35afb?raw)