List segments
Changed onRetrieve a paginated list of your customer segments with their mailable/textable member counts.
Rows carry each segment's name, prebuilt flag, and reachable-member counts but not its members: /v1/segments/{id}/contacts returns them. Nothing in the API reports performance per segment — there is no segment report, so revenue or engagement for a segment cannot be answered from here.
Required scope: segments_read
Request
- Base URLhttps://api.privy.com/v1
- AuthHTTP bearer
Query parameters
Page number (starts at 1).
Number of results per page. Values outside 10–100 are clamped to the nearest bound.
Headers
Target a subaccount instead of the main connected account. Pass a subaccount id from get_account's subaccounts list. Only direct subaccounts of the connected account are reachable — omit this for the main account itself.
Response
A paginated list of segments.
Example response
{
"data": [
{
"id": "Rz5T2kW8pB",
"name": "VIP Customers",
"total_count": 1930,
"mailable_count": 1240,
"textable_count": 315,
"counts": {
"refreshed_at": "2026-06-15T08:00:00Z",
"freshness": "Counts are refreshed periodically and may be up to an hour old."
},
"created_at": "2026-03-01T10:00:00Z",
"updated_at": "2026-06-01T10:00:00Z"
}
],
"pagination": {
"page": 1,
"per_page": 25,
"total_count": 142,
"total_pages": 6
}
}Changes
- info
added the optional property
//to the response with the status
- info
- warning
added the new
forbiddenenum value to the/response property for the response status - warning
added the new
forbiddenenum value to the/response property for the response status - warning
added the new
forbiddenenum value to the/response property for the response status - warning
added the new
segment_builder_requiredenum value to the/response property for the response status - warning
added the new
segment_builder_requiredenum value to the/response property for the response status - warning
added the new
segment_builder_requiredenum value to the/response property for the response status
- warning