🔔 Webhook Support for Multiple ABIs per Event Signature

Users can now track fungible and non-fungible token transfers more reliably — even when the same event signature (like Transfer) is used across multiple token standards.

What’s New

• 🔄 Multi-ABI Decoding: Webhooks now support decoding the same event signature using multiple ABIs. This is especially useful for events like Transfer that appear in both ERC-20 and ERC-721 contracts with different parameter structures.
• 💥 Fallback Decoding: If the first ABI fails to decode the event, we now try all provided ABIs until one succeeds — making decoding more robust.
• 🧪 Better Decoding for Edge Cases: For example, events with empty data fields ("0x") are now handled gracefully, and error handling during decoding has been improved.

🧠 AI Agent-Ready: Documentation Updates

We also updated the docs to help developers integrate with AI agents or build smart event-driven systems:

• Clearer instructions on setting up and managing webhooks via the Insight API
• New examples of multi-ABI event filters, including how to handle both ERC-20 and ERC-721 Transfer events
• Payload structure explained in more depth for downstream agent consumption

Don't forget to check the docs here!

Why It Matters

Many token standards reuse the same event signature hash (Transfer(address,address,uint256)), but the meaning and structure can differ. This update makes sure your webhook will correctly decode whichever version it encounters.

📌 Note: This feature is currently available via API only — improved UI/UX support for creating and managing multi-ABI filters is on the roadmap!

Let us know if you need help setting up multi-ABI filters for your use case — or if there’s another event format we should support next.