Overview
The Segments Members endpoint retrieves the complete list of people in a segment with their membership metadata. Results are paginated with a fixed page size of 5,000 members per page, making it efficient to export large segments or process members in batches. What You Get:- Complete list of Minerva PIDs for all segment members
first_added_attimestamp showing when each person initially joined the segment- Pagination metadata to traverse large segments
- Total member count across all pages
- Export segment membership for downstream processing or external systems
- Sync segment data to CRM platforms, marketing automation tools, or data warehouses
- Audit segment composition and membership history
- Feed Minerva PIDs into enrichment or signal monitoring workflows
- Generate reports on segment demographics or characteristics
Headers
Your API key for authentication
Query Parameters
The UUID of the segment to retrieve members from (obtained from the segments/create endpoint). The segment must exist and belong to your organization.
Page number for pagination, starting from 1 (not 0). Default is 1 if not specified. Each page returns up to 5,000 members (fixed limit).
Request Example
Response
Success Response
The API returns a paginated list of segment members with metadata.Unique identifier for this API request, useful for debugging and support
Paginated results object containing the member list and pagination metadata
ISO 8601 timestamp (YYYY-MM-DDTHH:MM:SS.ffffffZ format) when the request completed
Results Object Structure
Array of member objects for the current page. Maximum 5,000 items per page. Empty array if the segment has no members or you’ve requested a page beyond the last one.
Total number of members in the segment across all pages. This is the segment’s
current_size and represents the complete membership count.The current page number being returned (1-indexed). Matches the
page query parameter you provided.Indicates whether more pages exist.
true means you should request the next page to get additional members. false means this is the last page (or the only page).Member Object Structure
Each item in theitems array contains:
The Minerva person identifier for this segment member, in the format “p-”. Use this PID to enrich the person, retrieve their data, or remove them from the segment.
ISO 8601 timestamp showing when this person was first added to the segment. This timestamp is preserved even if the person is removed and re-added later, providing historical continuity.
- Page 1 of 3 (12,500 total members ÷ 5,000 per page = 3 pages)
- 3 members shown (truncated for readability; actual response would have up to 5,000)
list_continues: trueindicates more pages exist (pages 2 and 3)- Members are ordered by
first_added_atdescending (most recent additions first)
- Page 3 contains only 1 member (10,001 total = 5,000 + 5,000 + 1)
list_continues: falseindicates this is the final page
Pagination Guide
The endpoint uses a fixed page size of 5,000 members per page. To retrieve all members from a large segment: Algorithm:- Start with
page=1 - Process the
itemsin the response - Check the
list_continuesfield - If
true, increment page and repeat; iffalse, you’re done
- Total pages =
ceil(total_count / 5000) - Current page range =
[(page-1) * 5000 + 1, min(page * 5000, total_count)] - More pages exist =
page * 5000 < total_count
Error Responses
The API returns standard HTTP status codes with descriptive error messages:401- Unauthorized: Invalid or missing API key in x-api-key header404- Not Found: Segment with the providedsegment_iddoes not exist in your organization OR attempting to use v1 API version (only v2 supported)405- Method Not Allowed: Using POST, PUT, DELETE, or other methods (only GET supported)422- Unprocessable Entity: Missingsegment_idquery parameter OR invalidpageparameter (must be ≥ 1)500- Internal Server Error: Unexpected server error occurred
Error Examples
Segment not found:Implementation Notes
- API Version: Only v2 is supported. Using
/v1/segments/membersreturns a 404 error. - HTTP Method: Only GET requests are accepted.
- Page Size: Fixed at 5,000 members per page. This cannot be customized.
- Page Indexing: Pages are 1-indexed (first page is
page=1, notpage=0). - Ordering: Members are sorted by
first_added_atin descending order (most recent additions first). - Historical Timestamps: The
first_added_attimestamp is preserved across remove/re-add cycles, maintaining historical accuracy. - Empty Segments: If a segment has no members, you’ll get
items: [],total_count: 0, andlist_continues: false. - Out-of-Range Pages: Requesting a page beyond the last page returns empty
itemswithlist_continues: false.
Performance Characteristics
- Response Time: Typically 100-300ms per page
- Consistency: The
total_countis computed from the segment metadata table (current_sizefield), so it’s always accurate - Concurrency: Safe to paginate while other operations (add/remove members) are happening; you might see slightly inconsistent results across pages if the segment is being modified during pagination
- Rate Limiting: Standard API rate limits apply
Common Integration Patterns
Pattern 1: Export to CSVRelated Endpoints
- Add Members - Add people to the segment
- Remove Members - Remove people from the segment
- Enrich API - Get detailed data for the Minerva PIDs returned
- Death Signals - Get death signals for segment members

