---
title: "Bulk delete email-only users"
method: DELETE
path: "/v1/users/email-only/bulk"
tags: ["Schedule recipients"]
---

# Bulk delete email-only users

`DELETE /v1/users/email-only/bulk`

## Request

- Base URL: `https://blobsrus.omniapp.co/api`
- URL: `https://blobsrus.omniapp.co/api/v1/users/email-only/bulk`
- Auth: HTTP bearer

Delete up to 100 [email-only users](/administration/users/email-only) in a single request, identified by ID, by email, or a mix of both. Deleting an email-only user also removes them as a recipient from every schedule they receive.

If a request includes unknown or previously-deleted users, these users will be reported as `notFound` without blocking the rest of the request. 

Use the [Delete users](/api/users/delete-user) endpoint to delete standard users and [Delete embed users](/api/users/delete-embed-user) to delete embed users.

## Request body

- union
  - object
    - `emails` string[], required: Email addresses of the email-only users to delete
    - `userIds` string[]: IDs of the email-only users to delete. Use the [List email-only users](/api/users/list-email-only-users) endpoint to retrieve IDs.
  - object
    - `emails` string[]: Email addresses of the email-only users to delete
    - `userIds` string[], required: IDs of the email-only users to delete. Use the [List email-only users](/api/users/list-email-only-users) endpoint to retrieve IDs.

## Response `200`

The email-only users that were deleted, and any identifiers that didn't match an email-only user in your organization.

- object
  - `deleted` object[], required: The email-only users that were deleted
    - `email` string, email, required: Email address of the user
    - `userId` string, required: ID of the user
  - `notFound` object, required: Requested identifiers that didn't match an email-only user in the organization
    - `emails` string[], required: Requested emails that do not belong to an email-only user
    - `userIds` string[], required: Requested IDs that do not belong to an email-only user

## Other responses

- `400`: Bad Request. Possible error messages include: - `Invalid JSON` - Must provide at least one of `emails` or `userIds` - `emails: Invalid email address` - `userIds: Invalid uuid` - Maximum of 100 combined emails and user IDs can be processed in a single request
- `401`: Unauthorized - Invalid or missing API key
- `403`: Forbidden - insufficient permissions. Organization API keys are always allowed. [Personal Access Tokens (PAT)](/api/authentication#token-types) must have permissions to manage users, typically **Organization Admin**.
- `405`: Method Not Allowed - Invalid HTTP method for this endpoint
- `429`: Too Many Requests - Rate limit exceeded (60 requests/minute)

## Changes

- **2026-11-03** `43290040f88f`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/omni/apis/omni-api/changes/v1/users/email-only/bulk/delete.md)

---

[API](https://skmtc.dev/omni/apis/omni-api.md) - [All operations](https://skmtc.dev/omni/apis/omni-api/llms.txt) - [OpenAPI document](https://skmtc.dev/omni/apis/omni-api/revisions/43290040f88f?raw)