Webhooks

Observyze supports two types of webhooks: Event Webhooks (for outbound alerts) and Ingestion Webhooks (for inbound data from external platforms).

Event Webhooks (Outbound)

Configure webhooks in your Dashboard > Settings to receive POST requests when events occur (e.g. Budget Exceeded, Hallucination Detected).

Example Payload

{
  "event": "alert.triggered",
  "data": {
    "alert_id": "alt_123",
    "rule_name": "High Cost Alert",
    "organization_id": "org_123",
    "triggered_at": "2026-07-25T10:00:00Z",
    "message": "Monthly budget exceeded! Current spend is $50.00."
  }
}

Ingestion Webhooks (Inbound)

Send traces directly from other platforms into Observyze. Each mapping has its own revocable webhook credential and maps safe dot-path fields from the source payload into the Observyze trace schema.

Endpoint

POST https://api.observyze.com/api/v1/ingest/webhook/:mapping_id

Required Headers

X-Webhook-Key: ob_wh_your_mapping_key (or the same key as a Bearer token)
Content-Type: application/json

The plaintext mapping key is shown only when the mapping is created or its key is regenerated; only a bcrypt hash is stored. Tenant fields cannot be mapped from the payload, and the server always pins the trace to the mapping's organization and project before redaction and durable queueing.