# PROVISIONING_EMAIL_REQUIRED

With send_email set to true you must send email: without it there is nobody to send the link to.

<Callout type="info">
**Category:** [Accounts](/errors/category/account)
</Callout>

| | |
|---|---|
| HTTP status | `422` Unprocessable Content |
| Retry | After fixing the cause |

## When it happens

`send_email` is `true` and the request has no `email`, so there is nobody to send the claim link to.

## How to fix it

Send the holder's `email`, or set `send_email` to `false` and deliver the claim link yourself.

## Retry

Not as is: the same request fails the same way. Fix the cause described above, then send the request again, under a new `Idempotency-Key` if the body changed.

## Returned by

The operations where this code is most likely. The list is not exhaustive.

- [`POST /v1/accounts`](/accounts/provisionAccount)

## Example response

When this error occurs, the API answers `422` Unprocessable Content with a JSON body of this shape:

```json
{
  "type": "https://docs.beel.es/errors/PROVISIONING_EMAIL_REQUIRED",
  "title": "PROVISIONING_EMAIL_REQUIRED",
  "detail": "With send_email set to true you must send email: without it there is nobody to send the link to.",
  "instance": "/v1/<resource>",
  "errors": [],
  "success": false,
  "error": {
    "code": "PROVISIONING_EMAIL_REQUIRED",
    "message": "With send_email set to true you must send email: without it there is nobody to send the link to.",
    "details": {}
  },
  "meta": {
    "timestamp": "2026-05-21T10:00:00Z",
    "request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
  }
}
```

The `type` URI is stable and always resolves to this page.

## Message

<Tabs items={["English", "Spanish", "Catalan"]}>
  <Tab value="English">{"With send_email set to true you must send email: without it there is nobody to send the link to."}</Tab>
  <Tab value="Spanish">{"Con send_email a true hay que enviar email: sin él no hay a quién mandar el enlace."}</Tab>
  <Tab value="Catalan">{"Amb send_email a true cal enviar email: sense ell no hi ha a qui enviar l'enllaç."}</Tab>
</Tabs>

Send the request with `Accept-Language: <es|en|ca>` to receive the message in your preferred language.

## Other errors in this category

<div className="grid grid-cols-2 gap-3 not-prose">
  <Card title="CLAIM_TOKEN_EMAIL_REQUIRED" description="The account has no holder yet: send the email of the person who will claim it." href="/errors/CLAIM_TOKEN_EMAIL_REQUIRED" />
  <Card title="CLAIM_TOKEN_HOLDER_MISMATCH" description="That account already has a holder with a different email. Omit the field to re-issue the link to them." href="/errors/CLAIM_TOKEN_HOLDER_MISMATCH" />
  <Card title="DISPLAY_NAME_BLANK" description="The account name must not be blank." href="/errors/DISPLAY_NAME_BLANK" />
  <Card title="GRANT_ACCESS_LEVEL_INVALID" description="A grant's access level must be VIEW or OPERATE. To remove access to a company, omit it from the set." href="/errors/GRANT_ACCESS_LEVEL_INVALID" />
  <Card title="GRANT_COMPANY_NOT_IN_ACCOUNT" description="One of the specified companies does not belong to this account." href="/errors/GRANT_COMPANY_NOT_IN_ACCOUNT" />
</div>

## Keep exploring

<div className="grid grid-cols-2 gap-3 not-prose">
  <Card title="All Accounts errors" description="Every code in this category in one table." href="/errors/category/account" />
  <Card title="Error reference home" description="Browse every category or jump to the handling guide." href="/errors" />
</div>

---

Full OpenAPI spec: https://docs.beel.es/api/openapi