Reorder a completed fulfillment to a new date

Starts a new fulfillment workflow for an existing completed order,
replacing the visit date with new_date. Supports idempotency via
the Idempotency-Key header.

The original order must be in COMPLETED status and must belong to
the authenticated user and their campaign. The old tickets are voided
with the provider on a best-effort basis — if voiding fails the new
order still proceeds and the old tickets will expire naturally.

The response is synchronous and returns only the new fulfillment order
ID and the requested date. The actual ticket issuance is asynchronous.
Poll GET /fulfillment/orders/{order_id} (using the checkout order_id
of the new order) to retrieve tickets once the workflow completes.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

Request to reorder a completed fulfillment to a new date.

uuid
required

The order ID from the checkout confirmation of the completed fulfillment to reorder.

date-time
required

The new visit date and time in UTC (ISO 8601).

uri
required

Where the customer is redirected after completing a reorder
payment. Only used when the date change costs money; still
required so the payment flow can always be offered.

Headers
uuid
required

Client-generated UUID. Identical keys within the TTL window return the cached response.

string

RFC 7231 language preference. The best match against supported locales (nl-NL, en-GB, de-DE) is selected. Defaults to nl-NL when omitted.

string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json