> ## 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 un webhook de liste de leads

> POST /lead/{lead_id}/webhook/

Ajoute un webhook à une liste de leads, appelé avec la charge utile de l'entrée à chaque nouvelle soumission de formulaire.

<Note>
  Nécessite une clé d'API de gestion avec le quota `MANAGEMENT_API` (ou `MANAGEMENT_API_SANDBOX`) et la permission `LEAD_GENERATION_WEBHOOK_CAN_ADD`, 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 path="lead_id" type="string" required>
  Le `lead_id` de la liste de leads.
</ParamField>

<ParamField body="url" type="string" required>
  L'URL cible du webhook, jusqu'à 500 caractères.
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl --request POST \
    --url 'https://api.scanova.io/lead/L9c2f4a1e/webhook/' \
    --header 'Authorization: YOUR_API_KEY' \
    --header 'Content-Type: application/json' \
    --data '{ "url": "https://example.com/lead-webhook" }'
  ```
</RequestExample>

<ResponseExample>
  ```json 201 theme={null}
  { "id": 7, "url": "https://example.com/lead-webhook", "created": "2026-09-08T10:00:00+05:30", "modified": "2026-09-08T10:00:00+05:30" }
  ```
</ResponseExample>

`403` si le quota de webhooks par liste de leads du plan du compte est épuisé :

```json 403 theme={null}
{ "detail": "You have exhausted your limit of 5 webhooks.", "limit": 5 }
```

`404` si `lead_id` n'appartient pas à ce compte.

## Voir aussi

* [Lister les webhooks d'une liste de leads](/fr/api-reference/management-api/lead-webhooks/list) — voir ce qui est déjà configuré.
* [Mettre à jour un webhook de liste de leads](/fr/api-reference/management-api/lead-webhooks/update) — modifier l'URL d'un webhook.
* [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/{lead_id}/webhook/
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/{lead_id}/webhook/:
    post:
      summary: Create a lead list webhook
      operationId: createManagedLeadWebhook
      responses:
        '201':
          description: Webhook 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.

````