POST /v1/webhook_endpoints/{webhook_id}/disable - SEC API for AI

curl -X POST \
  -H "Authorization: Bearer $SECAPI_BEARER_TOKEN" \
  -H "secapi-version: 2026-03-19" \
  -H "content-type: application/json" \
  -d '{}' \
  "https://api.secapi.ai/v1/webhook_endpoints/wh_example_123/disable"

{
  "object": "webhook_endpoint",
  "id": "wh_2ZK8Q1W9F4M6P7R3",
  "createdAt": "2026-06-25T15:00:00.000Z",
  "updatedAt": "2026-06-25T15:00:00.000Z",
  "livemode": false,
  "orgId": "org_example_123",
  "description": "Production monitor matches",
  "destinationUrl": "https://example.com/hooks/secapi",
  "subscribedEventTypes": [
    "monitor.match",
    "webhook.test"
  ],
  "status": "disabled",
  "lastDeliveredAt": null,
  "requestId": "req_2ZK8Q1W9F4M6P7R3"
}

Disable a webhook endpoint without deleting delivery history

Audience: application and admin.

Pause without erasing evidence

Disable an endpoint to remove it from future fanout while retaining its configuration and recorded delivery history. This does not cancel a request that a remote receiver has already accepted.

Canonical metadata

requestId
traceparent

Example request

curl -X POST \
  -H "Authorization: Bearer $SECAPI_BEARER_TOKEN" \
  -H "secapi-version: 2026-03-19" \
  -H "content-type: application/json" \
  -d '{}' \
  "https://api.secapi.ai/v1/webhook_endpoints/wh_example_123/disable"

This organization control-plane action accepts bearer organization REST authentication. API keys cannot mutate webhook endpoints. The dashboard is optional.

Example response

{
  "object": "webhook_endpoint",
  "id": "wh_2ZK8Q1W9F4M6P7R3",
  "createdAt": "2026-06-25T15:00:00.000Z",
  "updatedAt": "2026-06-25T15:00:00.000Z",
  "livemode": false,
  "orgId": "org_example_123",
  "description": "Production monitor matches",
  "destinationUrl": "https://example.com/hooks/secapi",
  "subscribedEventTypes": [
    "monitor.match",
    "webhook.test"
  ],
  "status": "disabled",
  "lastDeliveredAt": null,
  "requestId": "req_2ZK8Q1W9F4M6P7R3"
}

Give this prompt to your agent

Failure posture

treat non-2xx responses as contract-aware failures, not free-form errors
preserve requestId and traceparent in logs and downstream reports
if provenance or freshness metadata is present, return it unchanged so trust is not lost in the handoff