Payload Format

When Transyt delivers a webhook to your application, it wraps the original provider payload in a standardized envelope format.

Envelope Structure

{
  "event_id": "550e8400-e29b-41d4-a716-446655440000",
  "provider": "stripe",
  "account_slug": "my-app",
  "event_type": "charge.succeeded",
  "external_id": "evt_1234567890",
  "payload": {
    "id": "evt_1234567890",
    "type": "charge.succeeded",
    "data": {
      "object": {
        "id": "ch_1234567890",
        "amount": 5000,
        "currency": "usd"
      }
    }
  }
}

Field Reference

Field	Type	Description
event_id	UUID	Transyt’s unique identifier for this event
provider	string	The provider that sent the webhook (e.g., stripe, mailgun)
account_slug	string	The account slug that received the webhook
event_type	string	The raw event type from the provider
external_id	string	The provider-specific deduplication ID
payload	object	The full, unmodified original webhook payload

Notes

• The payload field contains the exact original payload from the provider, unmodified
• The event_id is a UUID generated by Transyt — use this for idempotency on your side
• The external_id is provider-specific and may be a composite value (e.g., message-id:event for Mailgun)
• The event_type is the raw type from the provider; normalized types are available via the API