pickup_time_in_past

Why it happens

• "mode": "exact" with a pickupTime that is earlier than now.
• "mode": "deliver_by" with a time that passed.

A time zone mistake is a frequent cause. Times must be full ISO-8601 with an offset. Univooz rejects a time with no offset. A time in UTC with a local offset can be in the past.

How to fix it

Send a time in the future, with an offset:

{
  "mode": "exact",
  "pickupTime": "2026-07-29T14:00:00+02:00",
  "deliveryTime": "2026-07-29T15:00:00+02:00"
}

For the earliest possible collection, send { "mode": "asap" }. Univooz calculates the times and returns them in schedule.resolved.

A future time is necessary but not sufficient. The pickup must also obey the minimum notice period. See pickup_buffer_violation.

Example response

{
  "error": {
    "type": "invalid_request_error",
    "code": "pickup_time_in_past",
    "message": "The requested pickup time is in the past.",
    "param": "schedule.pickupTime",
    "doc_url": "https://docs.univooz.com/errors/pickup_time_in_past",
    "request_id": "req_01KZCCF8ZH4M7XQ2VB9RSTNPKD"
  }
}

Related

• pickup_buffer_violation
• Scheduling