> ## 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.

# List integration types

> GET /webhook/types/

Metadata for every supported `Webhook.type` — label, required fields, quota codename, and whether it's OAuth-based. Lets a client enumerate/validate types without hand-maintaining a shadow copy of what the backend already knows.

<Note>
  Requires a Management API key only — no additional permission gate.
</Note>

<RequestExample>
  ```bash cURL theme={null}
  curl --request GET \
    --url 'https://api.scanova.io/webhook/types/' \
    --header 'Authorization: YOUR_API_KEY'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  [
    {
      "type": "lead",
      "label": "Lead Notification Webhook",
      "required_fields": ["urls", "lead_list"],
      "quota_codename": "INTEGRATION_WEBHOOK",
      "is_oauth": false,
      "failure_threshold": 10
    },
    {
      "type": "hubspot",
      "label": "HubSpot",
      "required_fields": ["hubspot_connection"],
      "quota_codename": "INTEGRATION_HUBSPOT",
      "is_oauth": true,
      "failure_threshold": 10
    }
  ]
  ```
</ResponseExample>

`is_oauth: true` marks types whose *connection* is established through the browser OAuth flow in the dashboard, not through this API — see the [Management API overview](/api-reference/management-api/overview) for which parts of Slack/HubSpot integration are and aren't available here. `failure_threshold` is the number of consecutive delivery failures before the webhook is automatically disabled (its `status` becomes `stopped` and `last_used_status` records the reason).

## Related

* [List / create webhooks](/api-reference/management-api/integrations/webhooks-list-create) — `type` is required on create.
* [Management API overview](/api-reference/management-api/overview) — the auth scheme and quota architecture this endpoint is part of.


## OpenAPI

````yaml api-reference/openapi/management-api.json GET /webhook/types/
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:
  /webhook/types/:
    get:
      summary: List integration types
      operationId: listManagedWebhookTypes
      responses:
        '200':
          description: Metadata for every supported webhook type.
          content:
            application/json:
              example:
                - type: lead
                  label: Lead Notification Webhook
                  required_fields:
                    - urls
                    - lead_list
                  quota_codename: INTEGRATION_WEBHOOK
                  is_oauth: false
                  failure_threshold: 10
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.

````