---
title: "Remove Bulk Segment Members"
method: DELETE
path: "/v2/bulk/segments/members"
tags: ["Bulk Segment Operations", "Segments"]
---

# Remove Bulk Segment Members

`DELETE /v2/bulk/segments/members`

## Request

- Base URL: `https://api.attentivemobile.com`
- URL: `https://api.attentivemobile.com/v2/bulk/segments/members`
- Auth: one of:
  - HTTP bearer
  - OAuth 2
    - Authorization code: `https://ui-devel.attentivemobile.com/integrations/oauth-install?client_id={clientId}&redirect_uri={redirectUri}&scope={scope}`
    - Token URL: `https://api.attentivemobile.com/v1/authorization-codes/tokens` scopes: `segments:write`

Remove members from a segment in bulk. This endpoint accepts 1 to 10,000 members per request. Members are identified by email, phone number, and/or client user ID. The request is validated, queued for asynchronous processing, and a unique batch job ID is returned for tracking the status.

**Request Limits:**
- Minimum: 1 member per request
- Maximum: 10,000 members per request
- At least one identifier (email, phone, or clientUserId) required per member

**Processing:**
- Jobs are processed asynchronously
- Use the batch job ID to check status via `GET /v2/bulk/job/{bulkJobId}`
- Results available as downloadable `.jsonl` file when completed

Scopes Required: [segments:all]

Default Rate Limit: 100 requests per second

## Headers

- `Authorization` string, required

## Request body

- SegmentMembers
  - `externalId` string, required: The external ID of the segment. This is the client-provided unique identifier for the segment, as defined when creating the segment via the Segment API.
  - `members` SegmentMember[], required: Array of segment members to add or remove. Each member must have at least one identifier (email, phone, or clientUserId). Minimum 1 member, maximum 10,000 members per request.
    - `email` string, email: The member's email address. Use this to identify users by their email. At least one of email, phone, or clientUserId must be provided.
    - `phone` string: The member's phone number in E.164 format (e.g., +14155551234). At least one of email, phone, or clientUserId must be provided. **E.164 Format Requirements:** - Must start with '+' - Include country code - No spaces, dashes, or parentheses
    - `clientUserId` string: Your system's unique identifier for this user. Use this when you want to identify users by your own internal ID system. At least one of email, phone, or clientUserId must be provided. Maximum 100 characters.

## Response `202`

The bulk job request was successfully received and accepted for asynchronous processing. The response includes a batchJobId to track the status of the job, along with a confirmation message. Processing has not yet completed, please use the job status endpoint to monitor progress and retrieve results once available.

- BulkSuccessResponse
  - `message` string: A human-readable message confirming that the bulk job was successfully submitted.
  - `batchJobId` string: A unique identifier representing the submitted batch job. Use this ID to query the job's status, retrieve results, or diagnose any errors related to the job. This ID is returned upon successful job submission and required for all follow-up actions related to the batch.

## Other responses

- `400`: Invalid parameter in request query or body
- `401`: Unauthorized
- `403`: Access Denied
- `404`: The specified resource was not found
- `429`: The user has sent too many requests in a given amount of time
- `500`: Internal Server Error

## Changes

- **2026-11-03** `2f49ffff7d65`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/attentive/apis/attentive-api-v2/changes/v2/bulk/segments/members/delete.md)

---

[API](https://skmtc.dev/attentive/apis/attentive-api-v2.md) - [All operations](https://skmtc.dev/attentive/apis/attentive-api-v2/llms.txt) - [OpenAPI document](https://skmtc.dev/attentive/apis/attentive-api-v2/revisions/2f49ffff7d65?raw)