Creates a new order.
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.
Most document fields are optional. The backend resolves them in this order:
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.Client resolution is strictly deterministic:
clientId, the backend loads that client within the token scope,clientId, the client object is used for matching or creation,clientId and client, the client object is used only as a document snapshot override.Matching is deterministic and uses this order:
vatId, then countryId + subjectId, then name + email, then name + street,name + email, then name + street.An item can be created in three ways:
priceListItemId and quantity,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.
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.
Bearer token created for a specific company in Integrations → API.
Optional request identifier for safe retries. Use a unique value for each create request you want to retry safely.
"invoice-create-2026-03-03-001"
Payload used to create an order. The usual happy path is clientId plus items; the backend can resolve many other values automatically. You must send either clientId or the client object.
ID of an existing client. This is the recommended way to create an order. If you also send the client object, it is used only as a sparse snapshot override for this specific document.
101
Order items. This field is always required. Per-item uuid is not part of the request contract; if you send it, the backend ignores it. warehouseAllocations are not supported for orders.
1 - 100 elementsPayload for a single order line item. Three modes are supported: a manual item, priceListItemId + quantity, or priceListItemId with sparse override fields. quantity is always required. If you omit priceListItemId, you must also send name, unitPrice, and vatRate. unitId is optional; when you omit it for a manual item, the backend defaults to unit 1 (piece / Unit::Piece). If you send priceListItemId, the backend can hydrate the name, unit, unit price, and VAT rate from the price list item, and the payload then acts only as a sparse override.
Manual order number. If omitted, the backend generates it from the numbering series. If you send number, do not send numericalSeriesId in the same payload.
1 - 20"20260001"
Optional ID of the quotation the order is created from. The document must be available in the token scope and must not be linked to another order.
601
Sparse client payload. With clientId, it only overrides the snapshot stored on this document. Without clientId, the backend uses it to resolve or create the client.
Optional business case ID. When sent, it must be available in the token scope and to the client resolved as the final clientId.
701
Numbering series ID. If omitted together with number, the primary numbering series for orders is used. If you send numericalSeriesId, do not send manual number in the same payload.
12
Issue date in Y-m-d format. It must be after 2009-01-01 and before a date one year in the future. If omitted, the current date is used.
"2026-03-03"
Whole-document discount type.
percentage, fixed "percentage"
Whole-document discount value.
x >= 010
Reverse-charge flag. If omitted, false is used.
false
Delivery method ID from the delivery method reference table. Resolution priority is payload -> client preference -> company document settings.
1
Payment method ID from the payment method reference table. Resolution priority is payload -> client preference -> company document settings.
1
Currency ID from the currency reference table. Resolution priority is payload -> client preference -> company document settings.
1
Language ID from the language reference table. Resolution priority is payload -> client preference -> company document settings.
1
Document note. Resolution priority is payload -> client preference -> company document settings.
3000"Thank you for your order."
Text displayed above items. Resolution priority is payload -> client preference -> company document settings.
3000"Thank you for working with us."
The order was created.
Order.
501
"6b1b8c9e-66e6-4fb5-b2db-6d7c7f0f8f19"
"order"
"20260001"
Absolute URL of the public web document for this order.
"https://app.fintoro.sk/web-doklad/obj/4f3f8a95-5c4a-4c8b-9e6c-8a0c1a5df3a1"
Absolute URL of the Fintoro API endpoint that downloads this order PDF as an attachment.
"https://app.fintoro.sk/api/public/v1/orders/501/pdf"
Supplier snapshot stored directly on this document.
Live ID of the client linked to the order.
101
Historical client snapshot stored directly on this document.
"2026-03-03"
Optional business case ID. When sent, it must belong to the client selected on the document.
701
percentage, fixed "percentage"
10
false
12
Delivery method ID from the delivery method reference table.
1
Payment method ID from the payment method reference table.
1
Currency ID from the currency reference table.
1
Language ID from the language reference table.
1
"Thank you for your order."
"Thank you for working with us."
200
240
200
240
true