Soryxa Webhooks and Connectors

Inbound webhook path

Inbound connector webhooks use the integration slug and team public UUID. They can validate a direct email field or a nested action/data payload, and signed connectors are verified before work is queued.

POST /api/v1/integrations/webhook/{teamPublicUuid}/{slug}
Content-Type: application/json

{
  "action": "validate",
  "data": {
    "email": "user@example.com"
  }
}

Direct payloads with email or email_address are also accepted by connector-specific handlers where supported.

Outbound event shape

Store event IDs in receiving systems so duplicate deliveries can be handled safely. Inbound validate actions require an active outbound or bidirectional connector with read_results to receive results.

{
  "event": "validation.completed",
  "data": {
    "email": "user@example.com",
    "decision": "allow",
    "reason_code": "CLASSIFICATION_VALID",
    "score": 96
  }
}