Generic Provider

The generic provider is a flexible option for any webhook source that isn’t covered by a dedicated provider. It supports multiple authentication methods and auto-detects event IDs from common payload fields.

Authentication Methods

The generic provider checks for authentication in the following order:

1. Header-Based Authentication

Transyt checks these headers (in order):

Header	Description
x-webhook-secret	Direct secret comparison
x-api-key	API key comparison
x-secret	Secret comparison
x-signature	Signature comparison

2. Bearer Token

Authorization: Bearer {token}

3. URL Parameter

https://ingest.transyt.com/generic/{account-slug}?key=SECRET

All comparisons use constant-time algorithms to prevent timing attacks.

Setup

Point any webhook source at:

https://ingest.transyt.com/generic/{your-account-slug}

Include authentication via any of the methods above.

Account Configuration

curl -X POST https://ingest.transyt.com/admin/accounts \
  -H "X-Admin-Token: YOUR_ADMIN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "provider": "generic",
    "account_slug": "partner-system",
    "app_key": "my-app",
    "signing_secret_current": "shared-secret"
  }'

External ID Detection

The generic provider auto-detects event IDs from common payload fields, checked in order:

1. id
2. messageId
3. message_id
4. eventId
5. event_id
6. uuid
7. _id

If none of these fields exist, a fallback ID is generated: gen-{timestamp}-{payload_hash}.

Event Types

The generic provider preserves whatever event type information is available in the payload. No normalization is applied.