---
search:
  tags:
    - Custom audiences
    - POST
seo:
  description: >-
    Available on: Meta. Reference for the POST
    /mutations/{advertiserId}/custom-audiences endpoint in the AdCrunch API.
sidebar:
  label: Create a Custom Audience
  badge: POST
title: Create a Custom Audience
type: openapi-operation
---
**Available on:** [![Meta](/providers/meta.svg)](https://docs.adcrunch.dev/connect/providers)

Creates a Custom Audience. The body holds the fields of the new Custom Audience.

It starts a Mutation of the kind `meta_create_custom_audience`, the same change that `POST /mutations` starts with that kind. The MCP tool of the same name makes the same change.

Create a Meta Custom Audience. `source` selects what makes the audience: `website` (the visitors of a Pixel), `customer_list` (the emails and the phone numbers of your customers, sent to Meta as hashes) or `lookalike` (the people most like another audience, in one country). A Custom Audience has no status and starts no spend. An ad set uses it with customAudiences or excludedCustomAudiences. Meta can take some hours to populate a new audience, and a lookalike stays unusable until then.

The change does **not** happen during this request. The answer is `202`, and `Location` names the Mutation. Poll `GET /mutations/{id}` until it reports `complete` or `errored`. A Mutation is durable, so the id stays valid across retries and restarts.

A refused request starts nothing. AdCrunch refuses a body that does not match, an advertiser that is not yours, an advertiser with no usable connection, and an advertiser connected without write access before a Mutation exists. So a failed call leaves no row in the history.

**This operation checks the credential first and the body second.** A missing or unusable credential answers `401` even when the body is wrong as well.

`POST /mutations/{advertiserId}/custom-audiences`

**Request body** (`application/json`, required)

Request body example:

```json
{
  "excludeEvents": [
    "Purchase"
  ],
  "name": "Spring sale - Visitors 30 days",
  "pixelId": "812345678901234",
  "retentionDays": 30,
  "source": "website",
  "urlContains": [
    "example.com/spring-sale"
  ]
}
```

**Responses**

- `202` — The Mutation started, and it has not ended. The body is the answer of \`GET /mutations/{id}\`, with \`status\` of \`running\`. Poll the path in \`Location\` for the outcome.
- `400` — The request does not match the schema of this operation: a field is missing or has the wrong type, or the body is not valid JSON. \`error\` is \`invalid\_request\`, and \`issues\` names each field. Nothing was changed.
- `401` — No API key, or one that does not resolve. See the security scheme. \`error\` is \`unauthorized\`.
- `402` — The organization has no active subscription. An owner subscribes at \`paywallUrl\`. \`error\` is \`organization\_unentitled\`.
- `403` — The caller does not hold \`mutation:write\`, or the advertiser is connected without write access. In the second case \`error\` is \`missing\_write\_access\` and \`message\` says how to fix it. AdCrunch started nothing.
- `404` — The advertiser does not exist, it belongs to another organization, or it is not a Meta ad account. \`error\` is \`not\_found\` in each case. An advertiser that does not exist and an advertiser of another organization get the same answer on purpose, so a caller cannot learn which ids exist. AdCrunch started nothing.
- `409` — The advertiser has no usable connection: a person removed it, it expired, or the provider refused it. A person must connect it again. \`error\` is \`provider\_not\_connected\`, the code that a live read of Observe sends for the same failure. AdCrunch started nothing.

Response example, 202:

```json
{
  "mutationId": "mut_k3x9q2v7m4n8p1r5t6w0y2z4",
  "status": "running"
}
```
