FAQ

All Algorand transaction types: pay, axfer, appl, keyreg, acfg, afrz, and stpf. Each rule can filter by sender, receiver, asset ID, app ID, transaction type, and minimum amount.

No — each rule targets one sender and/or one receiver. Create separate rules for different addresses. All plans include multiple rule slots.

Each matching rule fires its own delivery independently. A single transaction can trigger webhooks to different endpoints if multiple rules match.

MainNet by default. The infrastructure supports TestNet and BetaNet via configuration — reach out if you need a non-MainNet instance.

Typically 200–500ms from block finalization to your endpoint, depending on network conditions and your server's location.

Failed deliveries retry automatically with exponential backoff. The maximum number of retries depends on your plan: 3 on Free, 5 on Hobby, 6 on Pro, 10 on Business. After exhausting retries, the delivery moves to a dead-letter queue where you can inspect and replay it from the dashboard.

A JSON body containing the event ID, rule name, network, round number, timestamp, and the full transaction object. Every request includes X-FalconHook-Signature (HMAC-SHA256) and X-FalconHook-Timestamp headers for verification. The signature is computed over "{timestamp}.{body}". See the docs for the complete schema.

Webhooks on all plans. Slack and Discord on Pro and above. Email notifications are coming soon for Business and Enterprise tiers.

Yes. Expose your local server with ngrok or localtunnel, register that URL as your endpoint, and you'll receive live webhooks during development.

Each webhook, Slack, or Discord notification sent counts as one delivery. Transactions that don't match any of your rules don't count toward your quota.

Excess deliveries are dropped for the remainder of the billing cycle. The quota resets on the 1st of each month (UTC). You can upgrade at any time to increase limits immediately.

Yes. Upgrades take effect immediately. Downgrades apply at the start of the next billing cycle.

7 days on Free, 14 on Hobby, 30 on Pro, 90 on Business, 365 on Enterprise. Only events that occurred while your rules were active are stored — we don't backfill historical chain data.

Keys are SHA-256 hashed before storage. Only a short prefix is kept for lookup. The raw key is shown once at creation and never stored or logged in plain text.

Every delivery includes X-FalconHook-Signature (HMAC-SHA256) and X-FalconHook-Timestamp headers. Compute the HMAC of "{timestamp}.{raw_body}" with your secret and compare using constant-time comparison. See the docs for examples in Python, Node.js, and Go.

No. We log delivery metadata (status codes, timestamps, latency) but not request bodies.