> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/developer/api/mep/custom-audience/1.0/delete.md). # DELETE - Remove The Custom Audience API 1.0 only accepts custom user IDs and avertising IDs. For audiences with install IDs, the version 1.1 should be used. The Custom Audience API enables you to create, update, delete and list custom audiences. A **custom audience** can contain a list of custom user IDs or advertising IDs (GAID or IDFA). This is useful to target segments with push notifications or In-App messages, either they are coming from your userbase or created by third-party tools. Custom audiences created using the API can be targeted from Batch’s dashboard or the Campaigns API. ### Request structure #### Route The Custom Audience API exposes a DELETE endpoint that allows to delete a custom audience : `https://api.batch.com/1.0/BATCH_API_KEY/custom-audience/AUDIENCE_NAME` Here is a valid cURL example: ```bash curl -H "Content-Type: application/json" -H "X-Authorization: BATCH_REST_API_KEY" -X DELETE "https://api.batch.com/1.0/BATCH_API_KEY/custom-audience/AUDIENCE_NAME" ``` The `AUDIENCE_NAME` value is the name of the existing audience you want this operation to be applied to. > **NOTE**: If the deleted custom audience is already used as a campaign targeting, Batch will consider it as an empty custom audience. The `BATCH_API_KEY` value is either your **Live**, **Dev** or **SDK** Batch API key from the settings page of your app within the dashboard (⚙ Settings → General). #### Headers In order to authenticate with the API, you need to provide your **company REST API Key** as the value of the `X-Authorization` header. You can find it in ⚙ Settings → General. ### Responses #### Success If the call to the API endpoint is successful you will receive an **HTTP 200** confirmation. #### Failure If the POST data does not meet the API requirements you will receive an actionable error message. Contact us at if you need further support. * `AUTHENTICATION_INVALID` (Http status code: 401, Error code: 10) * `API_MISUSE` (Http status code: 403, Error code: 12) * `ROUTE_NOT_FOUND` (Http status code: 404, Error code: 20) * `MISSING_PARAMETER` (Http status code: 400, Error code: 30) * `MALFORMED_PARAMETER` (Http status code: 400, Error code: 31) * `MALFORMED_JSON_BODY` (Http status code: 400, Error code: 32) * `SERVER_ERROR` (Http status code: 500, Error code: 1) * `MAINTENANCE_ERROR` (Http status code: 503, Error code: 2) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://doc.batch.com/developer/api/mep/custom-audience/1.0/delete.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.