API · Segments
List Segment Contacts
List contacts in a segment, newest membership first (requires full access). Use a contact ID as the pagination cursor.
GET
/segments/{id}/contactsFull accessRequest parameters
| Parameter | Type | Description |
|---|---|---|
idpath · required | string | Opaque resource id. |
limitquery · optional | integer1–100 Default: 20 | Number of results to return. See Pagination. |
afterquery · optional | string | Resource ID for the next page. Cannot be combined with before. See Pagination. |
beforequery · optional | string | Resource ID for the previous page. Cannot be combined with after. See Pagination. |
Request example
Set OPENSEND_BASE_URL=https://api.example.com and OPENSEND_API_KEY=os_replace_me on your server.
bash
curl -X GET "$OPENSEND_BASE_URL/segments/YOUR_id/contacts" \
-H "Authorization: Bearer $OPENSEND_API_KEY"Response
200 · application/json. Example IDs stand for IDs returned by your installation.
json
{
"object": "list",
"has_more": false,
"data": [
{
"id": "YOUR_ID",
"email": "you@example.net",
"first_name": "example",
"last_name": "example",
"created_at": "example",
"unsubscribed": false
}
]
}Behavior and errors
Ordering follows membership creation time, not contact creation time.
Use a full-access credential. List responses are newest first; use has_more and cursor IDs to continue. Resource IDs belong to your team; an unknown or foreign resource returns 404. See authentication, errors, rate limits, and compatibility for the shared contract.