Remove a contact from a segment
DELETE/api/v1/segments/{id}/contacts/{contact_id}
scope
contacts:writeTakes one contact out of the segment. The contact itself is not deleted. Returns 404 not_found if the contact was not in the segment.
Path parameters
| Name | Type | Description |
|---|---|---|
idrequired | string (uuid) | Segment id |
contact_idrequired | string (uuid) | Contact id |
Request
curl -X DELETE "https://your-crm.example.com/api/v1/segments/5e6f7a8b-9c0d-4e1f-8a2b-3c4d5e6f7a8b/contacts/9d7e4c11-5a2b-4f7c-8e3d-2a1b0c9d8e7f" \
-H "Authorization: Bearer $RAABTA_API_KEY"Errors
| Status | Code | When |
|---|---|---|
| 400 | validation_error | The body or query failed validation. `details` lists each failing field with a `path` and a `message`. |
| 401 | unauthorized | No usable API key: the Authorization header is missing or malformed, or the key is unknown, revoked or expired. The three are deliberately indistinguishable. |
| 403 | forbidden | The key is valid but lacks the scope this endpoint requires, or the request came from an address outside the key’s IP allowlist. The message says which. |
| 403 | account_suspended | The account this key belongs to is suspended. Rotating the key will not help; contact support. |
| 404 | not_found | No such resource in this account. A resource that exists in another account also returns this. |
| 429 | rate_limited | The per-key budget, or the per-IP budget for failed authentication, is exhausted. Honour `Retry-After` before retrying. |
| 500 | internal | Something failed on our side. Safe to retry with the same Idempotency-Key; quote `request_id` if it persists. |