Remove the booking contact
DELETE/v1/trips/{tripId}/contact
Removes the booking contact from the trip, as the contact panel's Remove does: their access to this trip and the contact details stored with it go; their account and their other trips stay. No undo, so confirm (a query parameter) must be the contact's email — the contact block's, or the account's when the block has none. Add a contact again with POST.
Permissions: travelers:write · Kind: destructive · Cost: 1 unit · MCP tool remove_trip_contact
Cannot be undone.
Path parameters
| Field | Type | Required | Description |
|---|---|---|---|
tripId |
uuid | yes |
Query parameters
| Field | Type | Required | Description |
|---|---|---|---|
confirm |
string | yes | The contact's email. max 200 chars |
Response 200
| Field | Type | Required | Description |
|---|---|---|---|
object |
"trip_contact" | 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