API reference

Segments

/groups

A segment is who a group-scoped event is about. A static segment keeps a list you add to; a dynamic segment holds whoever's attributes contain its filter, so nobody keeps it up. Beside the segments somebody keeps are temporary lists, picked by a person for one send: you can see them, but a key cannot change one and an event cannot name one. In the Subscription business pack a segment is, for example, “Annual plans”.

GET/groupsList · ?q ?external_ref ?temporary POST/groupsCreate GET/groups/{group_id}Read PATCH/groups/{group_id}Update · attributes replaced whole POST/groups/{group_id}/membersAdd members · up to 500 GET/groups/{group_id}/membersMembers · static DELETE/groups/{group_id}/members/{member_id}Remove a member POST/groups/syncBuild from an attribute GET/groups/{group_id}/matchesMatches · dynamicshown →POST/groups/{group_id}/deactivateDeactivate · no delete

GETList who a segment reaches

Requires groups:read. Who a dynamic segment holds right now: the active records whose attributes contain its filter — the same answer a send would get. A static segment is refused: ask /members.

Path parameters

group_iduuid · required

The segment id.

Query parameters

limitinteger · default 50 · max 200

offsetinteger · default 0

Returns

200 with an array of subscriptions or customers. 400 on a static segment.

Response body

A bare JSON array. Each item is one subscription: the same fields in every pack. Press Response on the sample to see one whole.

FieldTypeDescription

iduuid

tenant_iduuidThe instance.

external_refstring | nullYour own id, as you sent it.

display_namestring

attributesobjectShaped by the Subscription business pack's subject_schema.Varies by pack

statusactive | inactive

created_atdatetime

updated_atdatetime

On failure the body is { error, code } instead.

Previous← Authentication, keys and scopes NextEvent types →