Remove a traveler
DELETE/v1/travelers/{travelerId}
Removes a passenger from the trip, as the drawer's Delete does; the others close up the gap. Their app access, if any, is not revoked here — remove the booking contact for that. Undo with POST /changes/{changeId}/revert within 30 days, while its id is free and the headcount allows. An access email the write queued is not recalled.
Permissions: travelers:write · Kind: destructive · Cost: 1 unit · MCP tool remove_traveler
Undoable: the response carries Bymundi-Change-Id; revert it with POST /v1/changes/{changeId}/revert.
Path parameters
| Field | Type | Required | Description |
|---|---|---|---|
travelerId |
uuid | yes |
Query parameters
| Field | Type | Required | Description |
|---|---|---|---|
expectedUpdatedAt |
datetime | Refuse (409) unless the passenger still carries this updatedAt. |
Response 200
| Field | Type | Required | Description |
|---|---|---|---|
object |
"traveler" | yes | |
id |
uuid | yes | |
tripId |
uuid | yes | |
deleted |
true | yes |
Errors
Errors are problem details. Besides the refusals described above, any call like this one can return:
invalid_request— Invalid requestunauthorized— Missing or invalid API keyinsufficient_scope— Missing permissionrate_limited— Rate limit reachednot_found— Not foundidempotency_key_reused— Idempotency-Key reusedrequest_in_progress— Request in progressforbidden— Not allowed