invalid_time_range
The time window on GET /v1/orders is open or reversed.
Why it happens
You sent one update time only. Send updatedSince and updatedUntil together.
The end time is not after the start time. Such a window selects nothing.
Why an open window is not permitted. The window grows while you read it. If an order changes, it moves to the top of the list. You read that position already, so you never see the order.
The pickup and delivery filters have no pair rule. You can send one alone. They read planned times, and a planned time does not move.
How to fix it
Send both update times, and put the end time after the start time:
curl "https://api.univooz.com/v1/orders?updatedSince=2026-08-12T08:00:00%2B02:00&updatedUntil=2026-08-12T12:00:00%2B02:00" \
-H "Authorization: Bearer uv_live_YOUR_KEY"To read a long period, read one window to the end. Then move updatedSince to the old
updatedUntil. See Page through lists.
You can also send no time filter. Use this for the first call.
The param gives the field to correct.
Example response
{
"error": {
"type": "invalid_request_error",
"code": "invalid_time_range",
"message": "'updatedSince' must be sent together with 'updatedUntil'.",
"param": "updatedUntil",
"doc_url": "https://docs.univooz.com/errors/invalid_time_range",
"request_id": "req_01KZCCF8ZH4M7XQ2VB9RSTNPKD"
}
}