campaigns

GET /v1/campaigns/segments/{segmentId}

One saved segment.

All campaigns endpoints

All developer docs →

Authentication

Send an API key as a bearer token. The endpoint checks campaigns.view; a key without it is refused with 403, not 404.

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/{segmentId} \
  -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 as stored, including the filter tree. scope says who it may reach and cannot be changed after creation.

Parameters

NameTypeRequiredWhat it is
segmentId (path)stringYes—
org_id (query)stringNo—

Response

NameTypeRequiredWhat it is
idstringYes—
org_idstringYesThe segment's OWNER, not the orgs it selects.
scopestring<platform, reseller>Yes—
namestringYes—
descriptionstringNo—
definitionCampaignSegmentNodeYesA filter tree. Two node shapes and no third: a GROUP (op with children) or a CONDITION (field/operator/value). not takes exactly one child — an n-ary not reads as…
statusstring<active, archived>Yes—
created_bystringNo—
created_atstringNo—
updated_atstringNo—

Errors this endpoint can return

401 · 403 · 404