Skip to content

Complete a journey

Mark a journey as completed once the traveller has been dropped off.

Updated · 1 min read

You will mark a journey as completed after the drop-off, which closes it and makes it count towards your payout. You need an API key and a journey assigned to your company whose pickup time has passed.

Step 1: Complete the journey

When the traveller has been dropped off at the hotel, send the drop-off position:

PUT/journeys/488213/completeReference
Sign in to fill in your staging key. Sign in
curl --request PUT \  --url 'https://warpdrive.staging.transferz.com/transfercompanies/journeys/488213/complete' \  --header 'Accept: application/json' \  --header 'Content-Type: application/json' \  --header 'X-API-Key: YOUR_STAGING_API_KEY' \  --data '{  "latitude": 52.3738,  "longitude": 4.8862,  "recordedAt": "2026-12-01T14:28:00"}'
Response 204
HTTP/1.1 204 No Content

recordedAt is the moment of the drop-off, in UTC; leave it out to use the time of the request. The body is optional, but send the position.

Step 2: Check the result

You and the partner receive journeyStatusChangedEvent:

JSON
{  "journeyStatusChangedEvent": {    "created": "2026-12-01T14:28:03.114",    "journeyId": 488213,    "previousStatus": "JOURNEY_IN_PROGRESS",    "newStatus": "COMPLETED"  }}

COMPLETED is final. Stop sending positions and status updates for this journey.

Rules worth knowing

  • Not before the pickup time. A journey cannot be completed while its pickup time is still in the future.
  • Completing twice is harmless. If the journey is already COMPLETED, the call returns 204 and changes nothing. This also covers the case where Transferz completed the journey itself from the driver's position near the drop-off (see Report journey progress).
  • A no-show still needs completing. Reporting a traveller no-show through the API does not change the journey's status. Report it, then complete the journey; see Report a no-show or a delay.
  • Cancelled journeys cannot be completed.

Errors

StatusCodeCauseWhat to do
400COMPLETE_JOURNEY_NOT_ALLOWED_BEFORE_PICKUPThe pickup time is still in the future.Complete the journey after it has taken place.
400STATUS_TRANSITION_NOT_ALLOWEDThe journey was cancelled.Do not complete it; check the status with Get a journey.
400—latitude or longitude is missing from a body you sent.Send both, or no body.
403INSUFFICIENT_PERMISSIONSThe journey is not assigned to your company, or the id does not exist.Check the id.
401—The API key is missing, wrong or expired.See Authentication.

The error format is described in Errors.

Was this helpful?