INTEGRATIONS & ROUTING

Connect the systems you use.

Send events from your backend to public HTTPS receivers with the API or CLI. Use one destination or the outbound fan-out API to notify several destinations, with independent retries and delivery logs.

Public availability: outbound delivery is available on all plans. Incoming provider routing is not enabled for public use; the incoming sections below document the optional gateway and its limits.

OUTBOUND API

Send an event

Submit an authenticated event for a configured destination. Hookstride signs delivery, records attempts and retries eligible failures. No incoming gateway is required.

Send your first event →
OPTIONAL INCOMING GATEWAY

Route a provider's webhooks

When the gateway is enabled, verify a supported sender and route its events by type or trusted reference. Multiple matching routes can forward to different applications.

Configure incoming routing →

Incoming signature verification

These are the incoming signature formats Hookstride can verify directly when its optional gateway is enabled. Applications using other providers can still send verified events through the outgoing API.

SenderVerificationHow to connect
StripeEndpoint signing secretRegister the Hookstride source URL with Stripe, select its events, then save the endpoint's whsec_ secret.
GitHubWebhook secretRegister the source URL as a GitHub webhook and use the secret configured for that webhook.
PaystackWebhook signing secret (or legacy API key)Prefer the endpoint's whsec_ signing secret for timestamped Paystack webhooks. Legacy X-Paystack-Signature endpoints use a full-access sk_ API key; assess the credential risk before using that compatibility mode.
Custom HMACSigned JSONSign the raw JSON payload with the documented timestamp and HMAC-SHA256 scheme.

Using another service? Verify its webhook in your backend and submit the trusted event through the outgoing API. If you control the sender, it can also sign JSON using Hookstride's Custom HMAC contract. Selecting Custom does not verify a different provider's native signature.

Routing and delivery formats

Event-type routing

Route order.* to one application and customer.updated to another. Multiple matching rules can deliver to several destinations, subject to the configured fan-out limit.

Trusted reference routing

When applications share a sender account, use restricted reference-registration keys to bind an event reference to its intended application rather than trusting user-supplied app names.

Destination-specific payload format

Choose a standard envelope, a JSON representation of the original payload, or bounded field mapping. Every destination gets an independent Hookstride signature.

Current limits: arbitrary scripts, transformations that run user code and reproducing an upstream provider's native signature are not supported. The optional outbound fan-out endpoint can notify multiple project destinations in one atomic submission; each destination consumes one event allowance unit. Incoming routing rules and field mapping remain deliberately constrained.

Test with your application

Start with a receiver you control, verify signatures and record event IDs so retries remain safe.