---
search:
  tags:
    - Personas
    - POST
seo:
  description: >-
    Creates a Persona on a Brand. A Persona describes one audience that the…
    Reference for the POST /context/brands/{slug}/personas endpoint in the
    AdCrunch API.
sidebar:
  label: Create a Persona
  badge: POST
title: Create a Persona
type: openapi-operation
---
Creates a Persona on a Brand. A Persona describes one audience that the brand speaks to. The body and both ends of the age range are optional, because you write a Persona one part at a time. The slug is unique in the Brand, not in your organization. The answer is `409` if the slug already exists on this Brand.

`POST /context/brands/{slug}/personas`

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

- `age_max` (integer) — Upper age bound. Omit for "and older".
- `age_min` (integer) — Lower age bound. Omit for "and younger".
- `body` (string) — Who this audience is (markdown), at most 50,000 characters. Suggested headings: Profile, Motivations, Frictions, Language. Language means the words the audience itself uses, not a locale. The headings are advice, not schema.
- `description` (string, required) — One-line summary — what agents read to pick this Persona.
- `name` (string, required) — Display name.
- `slug` (string) — Optional explicit slug handle; normalized to kebab-case. Unique within this Brand, so two Brands may each hold the same one. Defaults to one derived from the name.

Request body example:

```json
{
  "age_max": 45,
  "age_min": 28,
  "body": "## Profile\n\nRunners of 40 to 80 kilometres a week, ten years in, with one pair in rotation and one on the shelf.\n\n## Motivations\n\nThey want the same shoe again, and proof that it is the same. A resole keeps them running on a pair they trust.\n\n## Frictions\n\nThey fear the new model is worse than the one they know. A change of sole or of last reads to them as a risk, not as progress.\n\n## Language\n\nThey say \"my daily trainer\" and \"I got 900 out of the last pair\". They ask about the drop and the stack, never about the technology.",
  "description": "Runners who already own a pair, and who buy the next one without looking at another brand.",
  "name": "Loyalists",
  "slug": "loyalists"
}
```

**Responses**

- `201` — The Persona as created, at \`revision\` 1. An unwritten body comes back \`null\`, which is a normal state rather than an error.
- `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 \`brand:write\`. \`error\` is \`forbidden\`.
- `404` — No Brand with that slug. \`error\` is \`not\_found\`.
- `409` — This Brand already has a Persona with that slug. \`error\` is \`slug\_conflict\`. Another Brand may hold the same one — the scope of the uniqueness is the Brand, not the organization.
- `422` — Two codes share this status. \`invalid\_slug\`: the name and slug carry no letter or digit. \`invalid\_age\_range\`: the minimum is above the maximum.

Response example, 201:

```json
{
  "ageMax": 45,
  "ageMin": 28,
  "body": null,
  "brandId": "brd_6a9c33",
  "createdAt": 1790000000000,
  "createdBy": "usr_4d8b12",
  "description": "Runners who already own a pair, and who buy the next one without looking at another brand.",
  "id": "psn_8c4a20",
  "name": "Loyalists",
  "revision": 1,
  "slug": "loyalists",
  "updatedAt": null
}
```
