Segmenting Contacts
Segmentation V2 APIs are now available! See the Getting Started guide to find out what new features are available.
Segments are similar to contact lists, except they update dynamically over time as information stored about your contacts or the criteria used to define your segments changes. When you segment your audience, you are able to create personalized Automation emails and Single Sends that directly address the wants and needs of your particular audience.
The Marketing Campaigns Segments API allows you to create, edit, and delete segments as well as retrieve a list of segments or an individual segment by ID.
Note that Twilio SendGrid checks for newly added or modified contacts who meet a segment's criteria on an hourly schedule. Only existing contacts who meet a segment's criteria will be included in the segment searches within 15 minutes.
Segments built using engagement data such as "was sent" or "clicked" will take approximately 30 minutes to begin populating.
Segment samples and counts are refreshed approximately once per hour; they do not update immediately. If no contacts are added to or removed from a segment since the last refresh, the sample and UI count displayed will be refreshed at increasing time intervals with a maximum sample and count refresh delay of 24 hours.
For more information on creating segments with the Twilio SendGrid Marketing Campaigns UI see "Segmenting your Contacts."
For help with Segmentation Query Language, see our Segmentation Query Language reference
Get List of Segments
The Segmentation v1 API was deprecated on December 31, 2022. Following deprecation, all segments created in the Marketing Campaigns user interface began using the Segmentation v2 API.
To enable manual migration and data retrieval, the GET and DELETE v1 API endpoints will remain available. The POST (create) and PATCH (update) v1 endpoints were removed on January 31, 2023 because it is no longer possible to create new v1 segments or modify existing ones. See our Segmentation v1 to v2 upgrade instructions to manually migrate your segments to the v2 API.
GET /v3/marketing/segments
Base url: https://api.sendgrid.com
This endpoint allows you to retrieve a list of segments.
The query param parent_list_ids is treated as a filter. Any match will be returned. Zero matches will return a response code of 200 with an empty results array.
parent_list_ids |
no_parent_list_id |
ids |
result |
|---|---|---|---|
| empty | false | empty | all segments values |
| list_ids | false | empty | segments filtered by list_ids values |
| list_ids | true | empty | segments filtered by list_ids and segments with no parent list_ids empty |
| empty | true | empty | segments with no parent list_ids |
| anything | anything | ids | segments with matching segment ids |
Authentication
- API Key
Headers
Query String
A list of segment IDs to retrieve. When this parameter is included, the no_parent_list_ids and parent_list_ids parameters are ignored and only segments with given IDs are returned.
A comma separated list of list ids to be used when searching for segments with the specified parent_list_id, no more than 50 is allowed
default: NoneIf set to true segments with an empty value of parent_list_id will be returned in the filter. If the value is not present it defaults to 'false'.
Responses
ISO8601 of created timestamp
format: date-timeThe id of the list if this segment is a child of a list. This implies the query AND CONTAINS(list_ids, ${parent_list_id})
ISO8601 timestamp the sample was last updated
format: date-timeISO8601 timestamp the object was last updated
format: date-timeISO8601 string that is equal to sample_updated_at plus an internally calculated offset that depends on how often contacts enter or exit segments as the scheduled pipeline updates the samples.
the error message
the field that generated the error
helper text or docs for troubleshooting
{
"errors": [
{
"field": "field_name",
"message": "error message"
}
]
}the error message
the field that generated the error
helper text or docs for troubleshooting
{
"errors": [
{
"field": "field_name",
"message": "error message"
}
]
}the error message
the field that generated the error
helper text or docs for troubleshooting
{
"errors": [
{
"field": "field_name",
"message": "error message"
}
]
}Need some help?
We all do sometimes. Get help now from the Twilio SendGrid Support Team.
Running into a coding hurdle? Lean on the wisdom of the crowd by browsing the SendGrid tag on Stack Overflow or visiting Twilio's Stack Overflow Collective.
