Segments
Get a segment
GET
/segments/{id}Needscontent.viewAuthorization
secretKeyheader
AuthorizationBearer <sk_…>A secret API key from Settings → API keys. It acts with its creator's role.
Path Parameters
id*integerThe segment's id.
Range
1 <= valueResponse Body
OK
application/json- response
segment*A saved, reusable audience.
Shell
curl -X GET 'https://app.cueston.com/api/segments/1'Example Response
JSON
{
"segment": {
"id": 42,
"name": "Workspace admins",
"description": "string",
"rules": {
"enabled": false,
"matchType": "all",
"rules": [
{
"id": "string",
"attribute": "string",
"operator": "equals",
"value": "string",
"key": "string"
}
]
},
"createdBy": {
"id": 42,
"name": "Ada Lovelace"
},
"createdAt": "2026-10-26T09:30:00Z",
"updatedAt": "2026-10-26T09:30:00Z",
"usage": [
{
"type": "string",
"id": 42,
"name": "Onboarding tour"
}
],
"liveUsage": 0
}
}Create a segmentPOST
A saved audience any content can target. At most 200 per workspace (`segment_limit`).
Update a segmentPATCH
Changes apply to drafts right away. Live content keeps the segment as it was when it was published, until you publish it again (its draft shows unpublished changes meanwhile).