> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scanova.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Créer une notification de leads

> POST /lead/notification/

Crée une notification programmée de rapport de leads.

<Note>
  Nécessite une clé d'API de gestion avec le quota `MANAGEMENT_API` (ou `MANAGEMENT_API_SANDBOX`) et la permission `LEAD_GENERATION_EMAIL_REPORT_CAN_CREATE_UPDATE`, envoyée comme valeur brute de l'en-tête `Authorization` — voir la [présentation de l'API de gestion](/fr/api-reference/management-api/overview).
</Note>

<ParamField body="name" type="string" required>
  Nom interne de la notification.
</ParamField>

<ParamField body="to" type="string" required>
  Adresse(s) e-mail du destinataire.
</ParamField>

<ParamField body="cc" type="string">
  Adresse(s) e-mail en copie.
</ParamField>

<ParamField body="bcc" type="string">
  Adresse(s) e-mail en copie cachée.
</ParamField>

<ParamField body="frequency" type="integer" required>
  L'une des valeurs `key` de [Lister les fréquences des notifications de leads](/fr/api-reference/management-api/lead-notifications/frequency).
</ParamField>

<ParamField body="lead_ids" type="array" required>
  Tableau de chaînes `lead_id` sur lesquelles porte cette notification. Écriture seule — la réponse reflète plutôt les listes résolues sous `lead_list`.
</ParamField>

<ParamField body="is_active" type="boolean" default="true">
  Si la notification est actuellement activée.
</ParamField>

<ParamField body="slack_workspace" type="integer">
  L'id d'un espace de travail Slack connecté, pour livrer aussi via Slack.
</ParamField>

<ParamField body="slack_channel_ids" type="array">
  Ids des canaux Slack où publier, lorsque `slack_workspace` est défini.
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl --request POST \
    --url 'https://api.scanova.io/lead/notification/' \
    --header 'Authorization: YOUR_API_KEY' \
    --header 'Content-Type: application/json' \
    --data '{
      "name": "Weekly Trade Show Report",
      "to": "sales@example.com",
      "cc": "manager@example.com",
      "frequency": 3,
      "lead_ids": ["L9c2f4a1e"],
      "is_active": true
    }'
  ```
</RequestExample>

<ResponseExample>
  ```json 201 theme={null}
  {
    "id": 12,
    "name": "Weekly Trade Show Report",
    "to": "sales@example.com",
    "cc": "manager@example.com",
    "bcc": null,
    "frequency": 3,
    "frequency_display": "Once a Week",
    "lead_list": [{ "lead_list_name": "Trade Show Signup", "lead_list_id": "L9c2f4a1e" }],
    "is_active": true,
    "slack_workspace": null,
    "slack_channel_ids": null,
    "created_by": { "id": 41, "email": "you@example.com" },
    "created": "2026-09-08T10:05:00+05:30",
    "modified": "2026-09-08T10:05:00+05:30"
  }
  ```
</ResponseExample>

`403` si le quota de notifications de leads du plan du compte est épuisé :

```json 403 theme={null}
{ "detail": "You have exhausted your limit of 3 email reports.", "limit": 3 }
```

## Voir aussi

* [Lister les notifications de leads](/fr/api-reference/management-api/lead-notifications/list) — voir ce qui est déjà configuré.
* [Lister les fréquences des notifications de leads](/fr/api-reference/management-api/lead-notifications/frequency) — valeurs `frequency` valides.
* [Présentation de l'API de gestion](/fr/api-reference/management-api/overview) — le schéma d'authentification et l'architecture de quotas dont fait partie cet endpoint.


## OpenAPI

````yaml api-reference/openapi/management-api.json POST /lead/notification/
openapi: 3.1.0
info:
  title: Scanova Management API (v2)
  description: >-
    The complete Scanova Management API — every endpoint available at
    api.scanova.io (QR codes, folders, tags, leads, forms, analytics, plans,
    shared users & roles), plus the token-creation and usage-stats endpoints
    used to authenticate against it. Every path and request/response shape below
    was verified live against a real API key and the actual running backend
    (Phase 7, 2026-08-16) — not guessed from reading urls.py alone.
  version: 2.0.0
servers:
  - url: https://api.scanova.io
    description: Management API — QR/folder/tag/lead/form/analytics/plans endpoints
security:
  - apiKeyAuth: []
paths:
  /lead/notification/:
    post:
      summary: Create a lead notification
      operationId: createManagedLeadNotification
      responses:
        '201':
          description: Notification created.
components:
  securitySchemes:
    apiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: >-
        Send your Management API key as the raw value of the Authorization
        header — no "Bearer " or "Token " prefix, and no other characters.
        Example: `Authorization: 401f7ac837da42b97f613d789819ff93537bee6a`. A
        header containing more than one space-separated part is rejected
        outright. Requests also require the request's Host header to be the
        management API host (e.g. api.scanova.io) — the same key sent to the
        regular API host will not authenticate.

````