Authentication
Send an API key as a bearer token. This endpoint does not state a specific permission in the specification, so give your key the least it needs and check the response rather than assuming.
Where your organisation id goes
This endpoint takes org_id as a query parameter. Leave it out and the call covers your whole tenancy subtree; send it to narrow the call to one organisation.
Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X GET https://api.zinndigital.com/v1/campaigns/segments \
-H "Authorization: Bearer zdk_live_…"Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
The segment library. Active segments by default; pass `status=archived` for the rest. A segment is never deleted, only archived — a campaign that has already been sent references the segment it was sent to, and deleting the row would erase the answer to "who did we mail?", which is the one question a complaint or an audit asks.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
org_id (query) | string | No | Which organization's campaigns to work on. Required only when you hold campaign access on more than one; staff always work on the platform scope and may omit it. |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
data | CampaignSegment[] | Yes | — |
Errors this endpoint can return
401 · 403 · 429