List orders

GET/v1/orders2 req/s

Query parameters

Parameter	Notes
`updatedSince`	Start of the update period. Inclusive. Send with `updatedUntil`.
`updatedUntil`	End of the update period. Exclusive. Send with `updatedSince`.
`pickupFrom`	Start of the pickup period. Inclusive. You can send it alone.
`pickupUntil`	End of the pickup period. Exclusive. You can send it alone.
`deliveryFrom`	Start of the delivery period. Inclusive. You can send it alone.
`deliveryUntil`	End of the delivery period. Exclusive. You can send it alone.
`status`	One order status.
`branch`	Branch reference or UUID.
`sort`	`updatedAt` (default) or `pickupTime`.
`limit`	Default 50, maximum 200.
`offset`	Default 0.

All times are ISO-8601 with an offset.

Univooz combines all parameters with AND.

{
  "data": [ { "reference": "ORD-260729-LD4Q" } ],
  "hasMore": true,
  "limit": 50,
  "offset": 0
}

data contains full order objects.

request_id is at the top level of the response. It is not in the orders inside data[].

One alone gives 422. See Page through lists for the reason and for a safe loop.

The pickup and delivery periods have no pair rule.

GET /v1/orders?pickupFrom=2026-08-12T08:00:00%2B02:00
              &pickupUntil=2026-08-12T12:00:00%2B02:00
              &sort=pickupTime

These periods read the planned times, not realPickupTime and realDeliveryTime. They show what must happen, not what happened.

This endpoint has the lowest limit on the API, because it is the status channel. See Rate limits.

For faster information, use webhooks.

branch accepts a closed branch, because a shop you closed still has orders to check. Order creation rejects a closed branch.
A branch value that matches nothing gives an error, not an empty page. A spelling mistake and a quiet week look the same otherwise.