Skip to content

Report a no-show or a delay

Report a traveller no-show or a driver who left the pickup, with photo evidence.

Updated · 3 min read

You will report that a traveller did not show up, attach evidence such as a photo of the empty meeting point, and close the journey. You need an API key and a journey assigned to your company. Reports like this are called actions.

Which actions you can report

TypeUse whenAccepted by the API
TRAVELLER_NO_SHOWThe traveller did not show up at the pickup.Yes
DRIVER_LEFT_PICKUPThe driver left the pickup location.Yes
DRIVER_DELAYEDThe driver is late.No
ADDITIONAL_PROOF_TRAVELLER_NO_SHOWExtra evidence for a no-show.No

The two types the API does not accept are set by other Transferz systems. To add more evidence to a no-show, upload another attachment to the same action instead.

Step 1: Report the stages first

A no-show is easiest to prove when the journey shows the driver on the way and at the pickup. Send driver underway and driver arrived, each with the driver's position, as described in Report journey progress. Transferz looks for both, with positions, plus a no-show action with at least one attachment.

Step 2: Create the no-show action

Send the journey id, the type and the driver's position where the no-show happened:

POST/actionsReference
Sign in to fill in your staging key. Sign in
curl --request POST \  --url 'https://warpdrive.staging.transferz.com/transfercompanies/actions' \  --header 'Accept: application/json' \  --header 'Content-Type: application/json' \  --header 'X-API-Key: YOUR_STAGING_API_KEY' \  --data '{  "journeyId": 488213,  "type": "TRAVELLER_NO_SHOW",  "position": {    "lat": 52.3094,    "lng": 4.7622  }}'
Response 200
{  "id": 140022,  "journeyId": 488213,  "created": "2026-12-01T15:32:10",  "updated": "2026-12-01T15:32:10",  "type": "TRAVELLER_NO_SHOW",  "attachmentFileIds": []}

Note that the position uses lat and lng here, not latitude and longitude. Keep the id: it is the action id you attach evidence to.

Step 3: Upload the evidence

Send the file as multipart/form-data in a part named file, one file per request. Accepted types are JPEG, PNG, WebP, GIF and PDF; HEIC photos are refused, so convert them first. Set the part's content type, such as image/jpeg.

POST/actions/140022/photoReference
Sign in to fill in your staging key. Sign in
curl --request POST \  --url 'https://warpdrive.staging.transferz.com/transfercompanies/actions/140022/photo' \  --header 'Accept: application/json' \  --header 'X-API-Key: YOUR_STAGING_API_KEY'
Response 200
HTTP/1.1 200 OK

The generated samples above leave out the file. This is the full request:

Sign in to fill in your staging key. Sign in
curl --request POST \  --url https://warpdrive.staging.transferz.com/transfercompanies/actions/140022/photo \  --header 'X-API-Key: YOUR_STAGING_API_KEY' \  --form 'file=@meeting-point.jpg;type=image/jpeg'

To add more evidence, upload each file with its own request to the same action.

Step 4: Check the action

List the actions of a journey to confirm the evidence arrived. page and size are required.

GET/actionsReference
Sign in to fill in your staging key. Sign in
curl --request GET \  --url 'https://warpdrive.staging.transferz.com/transfercompanies/actions?journeyId=488213&page=0&size=10&sort=created;desc' \  --header 'Accept: application/json' \  --header 'X-API-Key: YOUR_STAGING_API_KEY'
Response 200
{  "pagination": { "currentPage": 0, "pageSize": 10, "totalPages": 1, "totalResults": 1 },  "results": [    {      "id": 140022,      "journeyId": 488213,      "created": "2026-12-01T15:32:10",      "updated": "2026-12-01T15:33:02",      "type": "TRAVELLER_NO_SHOW",      "attachmentFileIds": [99331]    }  ]}

Step 5: Complete the journey

Reporting a no-show through the API does not change the journey's status. Complete the journey as usual; see Complete a journey.

Errors

StatusCodeCauseWhat to do
400INVALID_REQUESTjourneyId or type is missing.Send both.
500UNKNOWNA type other than TRAVELLER_NO_SHOW or DRIVER_LEFT_PICKUP was sent.Use one of the two accepted types. Do not retry unchanged.
400UNSUPPORTED_CONTENT_TYPEThe file is not a JPEG, PNG, WebP, GIF or PDF.Convert the file and send its content type with the part.
400—The part has no content type.Set the part's content type, such as image/jpeg.
4xx—The upload has no part named file, or the file is empty or too large.Send one non-empty file of at most 1 MB in a part named file.
403INSUFFICIENT_PERMISSIONSThe journey is not assigned to your company, or the id does not exist.Check the journey id and the action id.
401—The API key is missing, wrong or expired.See Authentication.

The error format is described in Errors.

Was this helpful?

Back to your build path: How a journey reaches you →