Webhooks

Available via: API only (private key X-Inflow-Api-Key)

Webhooks push event data to your server as things happen in Inflow. You register an HTTPS endpoint; when an event occurs, Inflow delivers a signed POST request through Svix.

In this section

Guide	Description
Overview & event types	What webhooks are, delivery format, full event catalog, merchant vs Connect events
Setting up webhooks	Register an endpoint, limits, retries, quick start
Verifying signatures	Validate `svix-id`, `svix-timestamp`, and `svix-signature` before processing
Managing webhooks	List, enable/disable, update subscriptions, delete, retrieve secret
Webhook best practices	Idempotency, fast `200` responses, monitoring

Quick start

curl -X POST https://api.inflowpay.xyz/api/webhook \
  -H "X-Inflow-Api-Key: inflow_prod_your_key" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://yourserver.com/webhooks/inflow"}'

Save the secret from the response — you need it to verify signatures.

Marketplace (Connect) accounts should subscribe to connect.* event types (see Overview & event types). Direct merchants use the unprefixed names (payment.settled, etc.).