Skip to main content
Status: Developer preview — contract-stable per @nexislabs/ai-platform v1; not yet serving public traffic.
Registers an outbound delivery endpoint for run progress. This is Praxa’s first outbound webhook lane — every existing integration in this corpus is inbound. Backed by two new tables, webhook_endpoints and webhook_deliveries.

Confirmed behavior

  • Deliveries are HMAC-signed.
  • Failed deliveries are retried with exponential backoff.
  • Deliveries that exhaust retries land in a dead-letter state.
  • Signing secrets are rotatable per tenant.

Authentication

Bearer API key, prefix praxa_sk_.

Request body

Gap. Neither source publishes field-level names for the registration request or response. The table below is this reference’s best-effort, clearly-flagged reconstruction from the confirmed behavior above and conventional webhook-registration shape — not a confirmed contract. Verify against the actual implementation before relying on exact field names.

Response (illustrative — not confirmed)

Delivery payload

Not specified by either source. The most defensible assumption is that deliveries carry the same AiPlatformEventV1 envelope documented in Events, since that is the platform’s one existing event schema — but this is an assumption, not a confirmed contract.

What is genuinely unresolved

  • Exact request/response field names for POST /v1/webhooks.
  • The HMAC signature scheme (header name, algorithm, canonicalization).
  • The retry schedule (attempt count, backoff base/cap) and how a dead-lettered delivery is surfaced to the tenant.
  • Secret-rotation mechanics (single active secret vs. overlap window).

Example

TypeScript