MyEZToll
PUT/api/partner/v1/bookings/{bookingId}

Update booking

Update a booking's dates and/or status.

Moving the window also moves that period's tolls: crossings the new window no longer covers leave the booking (to whichever booking does cover them, or to the owner), and crossings it now covers are pulled in. Tolls whose money was already taken never move — that needs a refund, not a date edit. The change is recorded in the security audit trail.

Authorization

X-Api-Key header

Send your partner key on every request. An owner key acts for its one owner; an integration token also needs the owner's id in the X-Owner-Id header.

Path parameters

bookingIdstringpathrequired

Body

application/json
dateFromstring <date-time>nullable
dateTostring <date-time>nullable
statusintegernullable

Response

200 · application/json
successbooleanrequired
dataobject
idstring
externalIdstringnullable

Your own booking id

carIdstring
carExternalIdstringnullable
renterIdstring
renterExternalIdstringnullable
dateFromstring <date-time>
dateTostring <date-time>
statusinteger

0=Init, 1=PendingApproval, 6=Approved, 7=Completed, 8=Draft, 17=Canceled.

statusNamestring
pricenumber
isApprovedboolean
sourcestringnullable

Where the booking came from (turo, hqrental, own, ...). A booking created through this API reads "own".

sourceReservationIdstringnullable

The reservation / trip number on that platform (e.g. the Turo trip id), when known.

errorstringnullable

Status codes

200The updated booking.
400Validation error.
401Missing, unknown or revoked API key.
404The resource does not exist under this owner.
409The new window would overlap another live booking of the same vehicle on hours the stored window did not already overlap. Overlap that already existed is left alone, so a booking recorded with a wrong end date can still be corrected. Nothing is saved when this is returned.