Orders
List orders
Returns a paginated list of orders in a lightweight preview shape. Use this endpoint for lists, synchronization, and quick overview use cases; use the order detail endpoint for the full document.
GET
List orders
Authorizations
Bearer token created for a specific company in Integrations → API.
Query Parameters
Filter by document number prefix. The backend uses prefix matching, not full-text or contains search.
Filter by client.
Issue date from.
Issue date to.
Minimum total amount excluding VAT after discounts.
Maximum total amount excluding VAT after discounts.
When true, only returns orders that do not yet have a linked final invoice.
When true, only returns orders that do not yet have a linked proforma.
Sort field.
Available options:
number, issueDate, total, totalWithVat Sort direction.
Available options:
asc, desc Number of results per page.
Required range:
1 <= x <= 500Page number.
Required range:
x >= 1Previous
Create orderCreates a new order.
### Recommended flow
The recommended happy path is to send `clientId` and `items`.
If the client does not exist in Fintoro yet, or you do not want to create it in a separate step, send a `client` object without `clientId`. The backend will try to match an existing client and create a new one only if nothing matches.
If you send both `clientId` and a `client` object, the `client` object acts as a sparse snapshot override for this specific order.
### How defaults work
Most document fields are optional. The backend resolves them in this order:
1. explicit payload value,
2. client defaults,
3. company document settings.
In practice this means for example:
- `number` and `numericalSeriesId` are resolved from the primary numbering series if you omit them,
- `issueDate` defaults to today,
- `transferTaxLiability` defaults to `false`,
- `deliveryMethodId`, `paymentMethodId`, `currencyId`, `languageId`, `note`, and `textAboveItems` can be resolved from client defaults or company document settings.
### How client resolution works
Client resolution is strictly deterministic:
- if you send `clientId`, the backend loads that client within the token scope,
- if you omit `clientId`, the `client` object is used for matching or creation,
- if you send both `clientId` and `client`, the `client` object is used only as a document snapshot override.
Matching is deterministic and uses this order:
- for companies: `vatId`, then `countryId + subjectId`, then `name + email`, then `name + street`,
- for people: `name + email`, then `name + street`.
### How item hydration works
An item can be created in three ways:
1. as a manual item with explicit name, unit, price, and VAT,
2. via `priceListItemId` and `quantity`,
3. via `priceListItemId` plus sparse overrides for selected fields such as price or name.
`priceListItemId` is used only for input hydration. The order response returns the final canonical item shape and does not echo this price list reference back as a separate field.
### Quotation link
Optional `quotationId` can be used to link the order to an existing quotation that is not already attached to another order.
If you send `Idempotency-Key`, the same key with the same payload returns the original response without creating a second order.
Next
List orders