Skip to content
Booking: Not started

Partner walk-through · Step 7 of 7

Cancel

Sample data. Nothing is sent to Transferz.

Why this step exists

If the trip is no longer needed, cancel the journey. Within the free cancellation window this costs nothing; after it, you must accept the charges.

The response shows the journey with its new status, so you can tell the traveller what it cost.

The request

POST/journeys/{journeyId}/cancelCancel journey in the reference

Step 3 has not been run yet, so this uses the sample journey. Run step 3 to use your own.

curl --request POST \  --url 'https://warpdrive.staging.transferz.com/partners/journeys/488213/cancel' \  --header 'Accept: application/json' \  --header 'Content-Type: application/json' \  --header 'X-Request-ID: req-ams-0001' \  --header 'X-API-Key: YOUR_STAGING_API_KEY' \  --data '{  "reason": "NOT_NEEDED_ANYMORE",  "acceptCharges": true}'
Sample data · nothing is sent

Common pitfall

After freeCancellationUntil, a cancel without acceptCharges: true fails with CANCELLATION_NOT_ALLOWED_FOR_JOURNEY. Read cancellationDetails first and only accept charges when the traveller agreed.

Ready to do this for real?

Sign in with the staging account Transferz set up for you. Then run the same calls against staging with your own key.

Was this helpful?