---
title: "Update a builder webhook destination"
method: PATCH
path: "/api/v1/webhooks/{id}"
tags: ["Webhooks"]
---

# Update a builder webhook destination

`PATCH /api/v1/webhooks/{id}`

Updates name, HTTPS URL, event types, or enabled state. URL changes force pending_verification and return a new verification token.

## Path parameters

- `id` integer, required

## Headers

- `Idempotency-Key` string

## Request body

- UpdateWebhookRequest
  - `name` string
  - `url` string, uri
  - `event_types` WebhookEventType[]
  - `enabled` boolean

## Response `200`

Webhook destination

- object
  - `object` 'webhook', required
  - `data` WebhookEndpoint, required
    - `id` integer, required
    - `object` 'webhook', required
    - `name` string, required
    - `url` string, uri, required
    - `event_types` WebhookEventType[], required
    - `status` 'pending_verification' | 'active' | 'disabled', required
    - `verified_at` string, date-time, nullable
    - `verification_token_expires_at` string, date-time, required
    - `failure_count` integer, required
    - `created_at` string, date-time, required
    - `updated_at` string, date-time, required
    - `retry_policy` WebhookRetryPolicy, required
      - `max_attempts` 8, required
      - `terminal_status` 'dead_letter', required
    - `signing_secret` string — Returned only on create or rotate-secret.
    - `verification` WebhookVerification
      - `token` string, required — One-time verification token returned only on create or URL change.
      - `expires_at` string, date-time, required
  - `meta` ResponseMeta, required
    - `request_id` string, required — Unique request ID (req_ prefix).
    - `cached` boolean, required
    - `cache_age_s` integer, nullable — Cache age in seconds, null if not cached.
    - `cost` integer, required — Advisory request weight (relative compute cost). 1 for simple reads; higher for heavier endpoints. Not a credit/price.
    - `directional_source` 'live' | 'degraded' — Which path produced the team-directional read on this response. Only present on endpoints that compute one (today: GET /api/v1/sports-edge-signals). "live" means the read RAN. "degraded" means it FAILED, so nothing was measured and the ranking fell back to raw conviction. The flag describes the READ, not its consequence: a read that ran and found nothing groupable also leaves the directional fields null, and that is honestly "live" -- the per-signal nulls already say "nothing to enrich here", so this snapshot-level flag carries only what they cannot, namely whether the read ran at all. A degraded response is cached on the shorter degraded TTL so it self-heals. Reported SEPARATELY from ranking_source because the two degradations are independent -- a smart-money DB miss weakens the ranking DATA, a directional failure removes a ranking WEIGHT -- and a consumer down-weighting a degraded response needs to know which input it lost. Omitted on endpoints that compute no directional read.
    - `ranking_source` 'live' | 'db_only' — Which ranking-data path produced this response. Only present on endpoints that can degrade a ranking (today: GET /api/v1/sports-edge-signals). "live" is the normal path (the current holder pile from the provider batch); "db_only" is the degraded fallback (a truthful but weaker trader_markets ranking) served when the live sharp-money ranking batch is unavailable (a smart-money DB read failure, not a Polymarket outage) and cached on a shorter TTL, so a consumer can down-weight or skip it. Omitted on endpoints that never degrade.

## Other responses

- `400` — Invalid request parameter
- `401` — Missing or invalid API key
- `402` — Active Insider subscription required
- `403` — Account access denied
- `404` — Resource not found
- `408` — Request exceeded the server's 30-second transport timeout. The timeout response has an empty body because it is generated before handler-level JSON error shaping.
- `409` — An Idempotency-Key request with the same body is still in progress. Retry shortly with the same key and body.
- `422` — The Idempotency-Key was already used with a different request body.
- `423` — Account is locked
- `429` — Rate limit exceeded. Two independent budgets. (1) 100 requests/minute per user (sliding window), on every authenticated route. (2) On the BATCH routes only: 2500 batch item units/minute per user, reserved before any item is executed. A batch with N requested items costs N item units, including duplicate and invalid items. 2500 = 100 requests x 25 items per batch, which is the most item work a key can buy through the request limiter at all: a caller may spend their entire 100-request minute on full 25-item batches without the item budget being what stops them. The REQUEST budget is the effective ceiling, and batching is never the more expensive choice. The item budget still denies at a sliding-window boundary (both counters carry the previous window forward with a floor, and the item counter runs 25x the request counter), so honor a 429 from either. Over-quota batches return 429 with Retry-After before any item work is done.
- `500` — Unexpected server error
- `503` — Redis-backed authenticated rate limiter unavailable; retry after the per-process outage cooldown

## Changes

- **2026-07-14** `22ab6cfbf300` — 3 warning, 61 info
  - added the new `insider_radar_flag_raised` enum value to the `data/event_types/items/` response property for the response status `200`
  - added the new `smart_money_flow_detected` enum value to the `data/event_types/items/` response property for the response status `200`
  - added the new `wallet_grade_changed` enum value to the `data/event_types/items/` response property for the response status `200`
  - added the new `insider_radar_flag_raised` enum value to the request property `event_types/items/`
  - …60 more
- **2026-06-01** `422bd4dc1611` — 81 warning, 4 info
  - added the new `account_locked` enum value to the `error/code` response property for the response status `400`
  - added the new `account_locked` enum value to the `error/code` response property for the response status `401`
  - added the new `account_locked` enum value to the `error/code` response property for the response status `402`
  - added the new `account_locked` enum value to the `error/code` response property for the response status `403`
  - …81 more
- **2026-05-08** `80e8658e5acf` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/0xinsider/apis/0xinsider-api/changes/api/v1/webhooks/:id/patch.md)

---

[API](https://skmtc.dev/0xinsider/apis/0xinsider-api.md) · [All operations](https://skmtc.dev/0xinsider/apis/0xinsider-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/0xinsider/0xinsider-api/revisions/dd8d0cd6ca4d/schema)