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

# Enable/disable or re-point a destination (alias of PUT)



## OpenAPI

````yaml /openapi.json patch /portal/api/destinations/{id}
openapi: 3.1.0
info:
  title: Hookie API
  version: 1.0.0
  summary: Capture, route and deliver webhooks.
  description: >-
    Hookie exposes three HTTP surfaces.


    **Ingest + streaming** is the public plane. A path-form endpoint URL
    authenticates by its own high-entropy slug — there is no key, token or
    cookie — and an `ik_live_…` ingest key authenticates the `/v1/*` routes.
    Whenever the URL names a dataset the payload is stored whole into it;
    project mapping rules are evaluated on exactly one shape, `POST
    /v1/ingest/{ingest_key}` with no dataset segment.


    **The customer portal API** is a separate, token-authed surface for your end
    customers, scoped to one portal and one customer.


    **The admin API** drives the console. It accepts either a browser session or
    an OAuth bearer token from a connected coding agent — the same routes, the
    same validation, the same audit trail. An agent's authority is its user's
    workspace role narrowed to the scopes granted in the console.


    This document is generated from the request handlers and adversarially
    verified against them.
  contact:
    name: Hookie
    url: https://hookie.ai
  license:
    name: Proprietary
    url: https://hookie.ai/legal/terms
servers:
  - url: https://app.hookie.ai
    description: Production
  - url: https://app.preview.hookie.ai
    description: Preview
security: []
tags:
  - name: Ingest
    description: Send events to Hookie.
  - name: Streaming
    description: Tail events in real time over SSE or WebSocket.
  - name: Portal
    description: Token-authed surface for your end customers.
  - name: Projects
    description: Projects and their settings.
  - name: Routing
    description: Rules, endpoints, datasets and records.
  - name: Delivery
    description: Destinations, deliveries and replay.
  - name: Workflows
    description: Multi-step workflows, triggers and AI agents.
  - name: Observability
    description: Search, correlation, stats and the audit log.
  - name: Workspace
    description: Members, connected agents, SSO and billing.
paths:
  /portal/api/destinations/{id}:
    patch:
      tags:
        - Customer Portal
      summary: Enable/disable or re-point a destination (alias of PUT)
      operationId: patchPortalDestination
      parameters:
        - name: id
          in: path
          required: true
          description: Destination id. Scoped to the token's tenant, portal and customer.
          schema:
            type: string
        - name: token
          in: query
          required: false
          description: >-
            Portal access token (hpt_…), as an alternative to the
            `Authorization: Bearer` header.
          schema:
            type: string
      requestBody:
        required: false
        description: >-
          Identical handler to PUT — PATCH is not a partial-update variant, it
          is the same code path. Only `enabled` and `url` are honoured; `name`
          and `dataset_filter` are ignored. An absent or unparseable body is
          treated as {}, which sets enabled = 1.
        content:
          application/json:
            schema:
              type: object
              additionalProperties: true
              properties:
                enabled:
                  type: boolean
                  description: >-
                    Only the literal JSON `false` disables; anything else
                    (including absence) sets enabled = 1.
                url:
                  type: string
                  format: uri
                  pattern: ^[Hh][Tt][Tt][Pp][Ss]://
                  description: >-
                    Applied only when it is a string starting with https://
                    (case-insensitive); otherwise silently ignored.
            example:
              url: https://hooks.acme.test/v2
      responses:
        '200':
          description: Updated.
          content:
            application/json:
              schema:
                type: object
                required:
                  - ok
                properties:
                  ok:
                    type: boolean
                    enum:
                      - true
              example:
                ok: true
        '401':
          description: >-
            Missing, malformed, revoked, expired token, or the portal is
            disabled.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: >-
            No destination matched this id for the token's tenant + portal +
            customer.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      security:
        - portalTokenHeader: []
        - portalTokenQuery: []
components:
  schemas:
    Error:
      type: object
      required:
        - error
      properties:
        error:
          type: string
          description: Human-readable reason.
        retry_after:
          type: integer
          description: Seconds to wait. Present on 429.
        upgrade_url:
          type: string
          format: uri
          description: Present only on a monthly-quota 429.
  securitySchemes:
    portalTokenHeader:
      type: http
      scheme: bearer
      description: >-
        A `hpt_…` customer portal token, as `Authorization: Bearer`. Stored
        hashed; shown once at issue.
    portalTokenQuery:
      type: apiKey
      in: query
      name: token
      description: >-
        The same portal token in the query string, for embedding the portal in
        an iframe where a header cannot be set.

````