Skip to main content
DELETE
Disable a webhook endpoint
Disable a tenant-owned Praxa webhook endpoint and verify that no later event delivery is attempted.
Availability: Partner preview. Required scopes: runs:write, runs:read.

Authenticate safely

Create a disposable personal workspace API key with exactly runs:write and runs:read. Send it as Authorization: Bearer $PRAXA_API_KEY. A Gateway OAuth token, Supabase JWT, provider credential, or organization memory key is not interchangeable with this key. The hosted playground sends the credential from your browser session to the documented API through the configured playground proxy. Use test data, never share the key, and revoke it when the check ends.

Request fields

string
required
endpointId path parameter.

Runnable request examples

What success means

A 204 response means the endpoint was disabled and intentionally has no response body.

Successful response

204 — Endpoint disabled.

Handle failures

Example problem

Verify the result

  1. List endpoints and confirm the target is no longer enabled.
  2. Trigger a disposable event and confirm no new delivery targets it.
  3. Remove the stored signing secret.

Retry, cleanup, and production use

  • Treat 401, 403, and 409 as authority or state signals, not generic retry prompts.
  • For 429 or retryable 5xx responses, follow server retry guidance and keep a bounded attempt budget.
  • Move the request into a trusted application backend before production; never ship the Praxa key in browser or mobile code.
  • Revoke the disposable key, disable test webhooks, and erase disposable candidate data after validation.
Continue with API authentication, the failure and retry guide, and the end-to-end coverage matrix.
Last modified on August 14, 2026