Get segment membership counts

API at a glance

Description: This API retrieves user counts for a specific segment across different channels. Supports asynchronous count refresh for real-time updates.

Authentication & testing

Testing the API on this page

How to try it here

  • Use your User API Key as the Username (leave Password blank).
  • Select the appropriate API endpoint based on your Blueshift region.
  • API - Select Region
  • Enter the necessary parameters and click Try It to run the request.
Authentication using Base64 encoding

Note for developers

API requests require authentication using HTTP Basic Authentication with an API key. The API key serves as the username, while the password field should be left empty. The format to encode is: your_api_key: (note the trailing colon).

This string must be Base64-encoded and included in the request's Authorization header as follows:

Authorization: Basic encoded_value

You can generate the encoded value using a trusted Base64 encoder.


Postman collection

Try it with Postman: Explore the API using Blueshift's Postman collection.


Things to know before you start

  • Asynchronous refresh: Use refresh=true to trigger a background count update. Poll with refresh=false to retrieve updated counts.
  • Refresh status: Response includes refresh_status which is refreshing (counts updating) or ready (counts available).
  • Channel counts: Returns counts for total users, email users, SMS users, push users, and in-app users.
  • Global inclusion: Use bypass_global=true to get counts without global inclusion segment filters.
  • Use case: Best for monitoring segment size, checking audience reach before campaigns, and tracking segment growth over time.

Request parameters

Check out the request parameters

Path parameters

ParameterTypeRequiredDescription
segment_uuidstring✅ YesUUID of the segment.

Query parameters

ParameterTypeRequiredDescription
refreshboolean❌ Notrue to trigger count update, false to retrieve counts. Updates happen asynchronously.
channelsstring❌ NoChannel to refresh counts for: users, email, push, sms, or inApp.
bypass_globalboolean❌ Notrue to return counts bypassing global inclusion segments.

Example requests & responses

Get segment counts
GET /api/v1/segments/{segment_uuid}/matching_users.json
{
  "refresh_status": "ready",
  "approxusers": 15000,
  "email_users": 12000,
  "sms_users": 8000,
  "push_users": 5000,
  "in_app_users": 3000,
  "approxusers_updated_at": "2021-08-25T06:06:59.412Z"
}
Trigger count refresh
GET /api/v1/segments/{segment_uuid}/matching_users.json?refresh=true&channels=email
{
  "refresh_status": "refreshing",
  "approxusers": 15000,
  "email_users": 12000,
  "sms_users": 8000,
  "push_users": 5000,
  "in_app_users": 3000,
  "approxusers_updated_at": "2021-08-25T06:06:59.412Z"
}
Path Params
string
required
Query Params
boolean
string
boolean
Responses

400

Bad request - The request was invalid or cannot be otherwise served. An accompanying error message will explain further.

404

Resource not found - Can happen due to resource conflicts. Re-try with exponential backoff. Contact us on [email protected] if the issue persists.

409

Conflict error, please retry - The request could not be completed due to a conflict with the current state of the target resource, re-try with exponential backoff.

429

Rate limit exceeded - Too many requests. Contact us on [email protected] for recommended throughput.

500

Internal Server Error - Please contact blueshift for more information.

502

Service unavailable, please retry - Bad Gateway, re-try with exponential backoff.

503

Service unavailable, please retry - Service Unavailable, re-try with exponential backoff.

504

Service unavailable, please retry - Gateway Timeout, please re-try with exponential backoff.

Language
Credentials
Basic
base64
:
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json