Skip to main content

Webhooks

Webhooks allow you to receive evaluation results as soon as they are ready. Instead of polling the API, configure an endpoint to receive HTTP POST requests with the evaluation result.

Configuration

Webhook endpoints are managed through the Triple Dashboard:

  1. Navigate to Settings > Webhooks
  2. Add your endpoint URL
  3. Copy your webhook signing secret for signature verification

Endpoint Settings

When creating or updating an endpoint, you can configure:

SettingRequiredDescription
urlYesThe HTTPS URL that will receive webhook POST requests
descriptionNoA human-readable label for the endpoint
rate_limitNoMaximum number of messages per second delivered to this endpoint
headersNoCustom HTTP headers included in every delivery (e.g., for additional authentication)
disabledNoSet to true to temporarily pause deliveries without deleting the endpoint

Secret Management

Each endpoint has a signing secret prefixed with whsec_. You can rotate the secret at any time from the Dashboard — a new secret is generated and the previous one is immediately invalidated.

Test Webhooks

You can send test webhook events to a specific endpoint from the Dashboard. Test events use the evaluation.finished event type and allow you to specify a confidence level and failed checks to verify your integration is working correctly.

Event Types

EventDescription
evaluation.finishedAn evaluation has finished and the result is now available

Payload

The webhook payload is the evaluation result. See Understanding the Result for the full payload structure, fields, and examples.

Signature Verification

Webhooks are signed using Svix. Each request includes svix-id, svix-timestamp, and svix-signature headers that you should verify to ensure authenticity.

Your endpoint's signing secret (prefixed with whsec_) is available in the Triple Dashboard under your endpoint's details. Svix provides open-source verification libraries for most languages. For manual verification, refer to the Svix documentation.

Delivery Attempts

You can view delivery attempts in the Triple Dashboard under your endpoint's details. Each attempt shows:

FieldDescription
Event typeThe event that triggered the delivery (e.g., evaluation.finished)
StatusWhether the attempt succeeded, failed, or is pending
Response codeThe HTTP status code returned by your endpoint
TimestampWhen the attempt was made