Meet and greet
Report that the host met the traveller for journeys with meet and greet.
You will record the moment your host or driver met the traveller, for example at the name sign in the arrivals hall. You need an API key and a journey assigned to your company.
A journey has meet and greet when its addonsPerQuantity contains MEET_GREET. The host waits with a
sign showing travellerInfo.meetAndGreetSignText at the journey's meetingPoint. Recording the
meeting tells Transferz when and where the traveller was met.
Step 1: Record the meeting
Send the position where the host met the traveller and the moment it happened:
/journeys/488213/host-traveller-metReferencecurl --request PUT \ --url 'https://warpdrive.staging.transferz.com/transfercompanies/journeys/488213/host-traveller-met' \ --header 'Accept: application/json' \ --header 'Content-Type: application/json' \ --header 'X-API-Key: YOUR_STAGING_API_KEY' \ --data '{ "latitude": 52.3094, "longitude": 4.7622, "recordedAt": "2026-12-01T13:48:00"}'HTTP/1.1 204 No ContentAll fields are optional. recordedAt is in UTC and defaults to the time of the request; a time in
the past is kept, so you can send the meeting after it happened. Send both coordinates or neither.
Step 2: Check the journey
Get a journey now returns the meeting:
{ "hostTravellerMetTime": "2026-12-01T13:48:00", "hostTravellerMetPosition": { "latitude": 52.3094, "longitude": 4.7622 }}Rules worth knowing
- Before the ride starts. The meeting can be recorded while the journey is
CONFIRMED,PLANNED,DRIVER_UNDERWAYorDRIVER_ARRIVED; not once it isJOURNEY_IN_PROGRESS, completed or cancelled. Record it before you send in progress. - Once only. The first record stands; a second call is refused.
- No status change and no event. The journey keeps its status, and no webhook event is sent to you or the partner. Report the stages separately; see Report journey progress.
Errors
| Status | Code | Cause | What to do |
|---|---|---|---|
400 | HOST_TRAVELLER_MET_NOT_ALLOWED_FOR_STATUS | The journey is in progress, completed or cancelled. | Record the meeting before the traveller boards. |
400 | HOST_TRAVELLER_MET_ALREADY_RECORDED | The meeting was already recorded. | Nothing to do; the first record stands. Treat it as success when retrying. |
400 | HOST_TRAVELLER_MET_TIME_IN_FUTURE | recordedAt is later than now. | Send the time in UTC, or leave recordedAt out. |
403 | INSUFFICIENT_PERMISSIONS | The 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.