---
title: "Bulk delete custom field options"
method: DELETE
path: "/v3/custom_field_options/bulk"
tags: ["Custom Field Options"]
---

# Bulk delete custom field options

`DELETE /v3/custom_field_options/bulk`

Asynchronously archive many options at once by id. Like the single-resource DELETE, this is a soft archive — rows are flagged `active: false`, historical selections are preserved, and archived options are still returned by the list endpoint unless `active=true` is passed. Per-item success or failure is reported through the bulk-status endpoint.

## Request body

- object
  - `callback_url` string — Optional HTTPS URL Greenhouse will POST to when every row in `data` has finished. Omit to poll `GET /v3/bulk_requests/{bulk_action_uuid}` instead.
  - `data` number[], required — Array of integer ids identifying the records to delete. Each id is dispatched to the matching non-bulk DELETE endpoint in its own Sidekiq job.

## Response `202`

Accepted

- object
  - `bulk_action_uuid` string — UUID assigned to the new bulk request. Use this with `GET /v3/bulk_requests/{bulk_action_uuid}` to monitor progress and retrieve per-row results.
  - `status` string — Initial lifecycle state of the new bulk request, typically `building` immediately after creation. See the bulk request response schema for the full set of values.
  - `status_url` string — Relative path that returns the current status of the bulk request. Append this to your Harvest base URL to fetch the latest state.

## Other responses

- `401` — Unauthorized
- `413` — Payload is larger than 10MB
- `422` — Validation Error
- `429` — Client has more than 5 active jobs

---

[API](https://skmtc.net/greenhouse/apis/auth-api.md) · [All operations](https://skmtc.net/greenhouse/apis/auth-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/greenhouse/auth-api/versions/9517a2e54640/schema)