Skip to content

Change a journey

Change a journey's details or add-ons, and settle any extra payment.

Updated · 4 min read

You will change a booked journey, such as its pickup time, traveller details or add-ons, and pay any extra cost. You need the journey id and a journey that has not started yet.

Step 1: Check which add-ons can be added

Skip this step if you do not change add-ons. Get available add-ons lists the add-ons for this journey, how many are booked now and the most that are allowed:

GET/journeys/488213/available-addonsReference
Sign in to fill in your staging key. Sign in
curl --request GET \  --url 'https://warpdrive.staging.transferz.com/partners/journeys/488213/available-addons' \  --header 'Accept: application/json' \  --header 'X-API-Key: YOUR_STAGING_API_KEY'
Response 200
{  "combinedSeatBasedAddonCapacity": 2,  "availableTravelAddons": [    { "type": "MEET_GREET", "maximumAllowedAmount": 1, "currentlySelectedAmount": 1 },    { "type": "CHILD_SEAT", "maximumAllowedAmount": 2, "currentlySelectedAmount": 0 },    { "type": "BABY_SEAT", "maximumAllowedAmount": 0, "currentlySelectedAmount": 0 }  ]}

An add-on with maximumAllowedAmount 0 cannot be booked for this journey. The answer is 204 No Content when no add-ons can be offered. CARBON_EMISSION_COMPENSATION cannot be added in a change.

Step 2: Send the change

Send only what changes to Create journey change. This example moves the pickup to 15:15 and adds a child seat:

POST/journeys/488213/changesReference
Sign in to fill in your staging key. Sign in
curl --request POST \  --url 'https://warpdrive.staging.transferz.com/partners/journeys/488213/changes' \  --header 'Accept: application/json' \  --header 'Content-Type: application/json' \  --header 'X-API-Key: YOUR_STAGING_API_KEY' \  --data '{  "pickupDate": "2026-12-01T15:15:00",  "travelAddons": [    {      "type": "MEET_GREET",      "amount": 1    },    {      "type": "CHILD_SEAT",      "amount": 1    }  ]}'
Response 200
{  "changeId": 20417,  "additionalPaymentRequired": true,  "previousPrice": { "price": 72, "priceVat": 5.94, "commission": 7.2, "commissionVat": 0, "currency": "EUR" },  "newPrice": { "price": 82, "priceVat": 6.77, "commission": 8.2, "commissionVat": 0, "currency": "EUR" }}

What you can change:

FieldNotes
pickupDateThe new local pickup time.
travellerInfoTraveller details, passengers and luggage. email is required in this object, so send the traveller's details as they should be after the change.
origin or destinationOnly the end that is not the hub. For a journey from the airport, only the destination can change.
travelAddonsThe complete list of add-ons after the change. It replaces the current list: include the add-ons the journey already has. An empty list removes all add-ons; leaving the field out keeps them.

Transferz prices the changed journey. If the price does not go up, the change is applied at once and the response has additionalPaymentRequired false and no prices:

POST/journeys/488213/changesReference
Sign in to fill in your staging key. Sign in
curl --request POST \  --url 'https://warpdrive.staging.transferz.com/partners/journeys/488213/changes' \  --header 'Accept: application/json' \  --header 'Content-Type: application/json' \  --header 'X-API-Key: YOUR_STAGING_API_KEY' \  --data '{  "travellerInfo": {    "firstName": "Alex",    "lastName": "Traveller",    "email": "alex.traveller@example.com",    "phone": "+447700900123",    "driverComments": "Two suitcases, a stroller and a folded wheelchair.",    "flightNumber": "TZ1234"  }}'
Response 200
{  "changeId": 20418,  "additionalPaymentRequired": false,  "previousPrice": null,  "newPrice": null}

If the price goes up, the change waits until the difference is paid. Show the traveller previousPrice and newPrice, and continue with the next step when they agree. If they do not, do nothing: the journey keeps its current details.

Step 3: Pay the extra cost

Only needed when additionalPaymentRequired is true. Use the changeId from the response.

On invoice: call Pay journey change on invoice. It pays the difference on your invoice and applies the change. The response is 200 with no body.

POST/journeys/488213/changes/20417/pay-by-invoiceReference
Sign in to fill in your staging key. Sign in
curl --request POST \  --url 'https://warpdrive.staging.transferz.com/partners/journeys/488213/changes/20417/pay-by-invoice' \  --header 'Accept: application/json' \  --header 'X-API-Key: YOUR_STAGING_API_KEY'

With a payment link: call Generate journey change payment link and send the booker to the url. The change is applied once the booker has paid.

POST/journeys/488213/changes/20417/generate-payment-linkReference
Sign in to fill in your staging key. Sign in
curl --request POST \  --url 'https://warpdrive.staging.transferz.com/partners/journeys/488213/changes/20417/generate-payment-link' \  --header 'Accept: application/json' \  --header 'X-API-Key: YOUR_STAGING_API_KEY'
Response 200
{  "url": "https://test.adyen.link/PLTZ7K4QM0002",  "expiresAt": "2026-11-28T16:20:00"}

Step 4: Confirm the result

Call Get journey to check the new details, and get the voucher again: a change issues a new voucher. Tell the traveller what changed.

When a journey can be changed

  • Only before the journey starts. Changes are refused for a journey that is in progress, completed or cancelled.
  • Only until shortly before pickup. After the modification window closes, the API refuses changes; contact Transferz customer service instead.
  • Some changes cannot be made automatically; the API then refuses them with JOURNEY_CHANGE_ERROR and Transferz customer service can help.

Errors

ProblemCauseWhat to do
400 with NO_CHANGES_SUPPLIEDNothing in the request changes the journey.Send at least one changed field.
400 with INVALID_JOURNEY_STATUSThe journey has started, is completed or is cancelled.Fetch the journey to check its status.
400 with INVALID_LOCATIONThe change moves the hub end of the journey.Change only the end that is not the hub, or cancel and book again.
400 with QUOTE_GENERATION_FAILEDNo price could be calculated for the new details.Try another time or address, or cancel and book again.
400 with JOURNEY_CHANGE_ERRORToo late to change, or the change cannot be made automatically.Contact Transferz customer service.
400 with JOURNEY_CHANGE_NOT_ALLOWED_AFTER_MODIFICATION_WINDOWThe window closed before the change was paid.Contact Transferz customer service.
400 with JOURNEY_CHANGE_NOT_ALLOWED_WHEN_MINIMUM_NOTICE_EXCEEDEDThe new pickup time is too soon.Choose a later pickup time.
400 with JOURNEY_CHANGE_WRONGThe changeId belongs to another journey.Use the journey id and change id from the same change.
400 with PAYMENT_ON_INVOICE_NOT_ALLOWEDInvoice payment is not enabled for your account.Use a payment link.
403 with INSUFFICIENT_PERMISSIONSThe journey belongs to another partner.Check the journey id and the API key.
404 from a payment callNo change with this id.Check the changeId.

Next steps

Was this helpful?

Back to your build path: How a booking works →