Tillo webhook information

🌟 Checkout our API documentation for detailed instructions on how to set up your first webhook: https://tillo.tech/v2_docs/webhooks.html#webhook-structure

What is a Webhook?

 A webhook is a way for Tillo to talk to your system automatically as soon as something happens.

📭 Think of the standard API process like checking your mailbox every hour to see if a package has arrived (this is called "polling"). It’s time-consuming and often results in empty trips. 

📬 A Webhook, on the other hand, is like having a smart doorbell that pings your phone the exact second the package is dropped off.

Source: Introducing Real-Time Brand Status Updates via Webhooks

Available webhooks

• Brand Status webhooks: Notifies you when a brand’s status changes, for example if a brand is temporarily down or disabled, so you can take immediate action on your side (hide the brand, pause sales, switch routing, etc.)
• Brand Denomination Changes webhooks: Notifies you when a brand’s fixed denominations change, so you can automatically add, remove, or update the denominations you show in your app and reduce issuance failures caused by stale catalog data.
• Float Balance Alert webhooks: Notifies you when your float drops below a threshold so you can automate internal alerts or trigger a top-up flow (for example by calling the Request Float Payment Transfer endpoint).

There is also a separate set of StoreFront transactional webhooks which are distinct from the above.

Why you should use webhooks:

• Faster updates (near real-time): You receive important events as they happen, like denominations becoming out of stock or a brand being temporarily disabled.
• More reliable than polling: Constantly calling an API to “check status” can miss edge cases, run into rate limits, or introduce delays. Webhooks reduce that risk.
• Better customer experience: Your customers get quicker confirmations and fewer “please wait” moments, especially for async or delayed processes.
• Lower system load and cost: Fewer repeated API requests, less unnecessary processing, and cleaner integrations.
• Clearer automation: Webhooks make it easier to build event-driven workflows, like auto-reconciling orders, flagging failures, or triggering support workflows.