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

# List registered hooks

> List registered hooks plus the per-topic verifier bindings.

With a topic, lists only the hooks registered for that topic; without one,
lists every registered hook. The response carries the hooks under ``items``
(with ``total``), the per-topic verifier bindings under ``topic_verifiers``, and
under ``trigger_auth`` how a topic's webhook ingress door authenticates its caller —
DERIVED from the live verifier bindings just read, never stored. ``trigger_auth`` is
keyed by every topic among the LISTED hooks plus every topic currently carrying a
verifier binding (one may be bound before any hook exists on it), so under a
``topic`` filter it is neither a subset nor a superset of the listed topics.



## OpenAPI

````yaml /openapi.json get /api/hooks
openapi: 3.1.0
info:
  description: The operator HTTP surface served under /api/*.
  title: tai42-skeleton API
  version: 0.1.1
servers: []
security: []
paths:
  /api/hooks:
    get:
      tags:
        - hooks
      summary: List registered hooks
      description: >-
        List registered hooks plus the per-topic verifier bindings.


        With a topic, lists only the hooks registered for that topic; without
        one,

        lists every registered hook. The response carries the hooks under
        ``items``

        (with ``total``), the per-topic verifier bindings under
        ``topic_verifiers``, and

        under ``trigger_auth`` how a topic's webhook ingress door authenticates
        its caller —

        DERIVED from the live verifier bindings just read, never stored.
        ``trigger_auth`` is

        keyed by every topic among the LISTED hooks plus every topic currently
        carrying a

        verifier binding (one may be bound before any hook exists on it), so
        under a

        ``topic`` filter it is neither a subset nor a superset of the listed
        topics.
      operationId: get_api_hooks
      responses:
        '200':
          content:
            application/json:
              schema:
                properties:
                  data: {}
                required:
                  - data
                type: object
          description: Success.
        '401':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
          description: Missing or invalid api key.
      security:
        - ApiKeyAuth: []
components:
  schemas:
    Error:
      properties:
        error:
          type: string
      required:
        - error
      type: object
  securitySchemes:
    ApiKeyAuth:
      in: header
      name: x-api-key
      type: apiKey

````