Swapcard's webhook system is a powerful tool for real-time integrations — but like any powerful tool, it needed a guardrail. Starting now, each customer account is limited to 20 webhook subscriptions per event. It's a small number that makes a big difference.

What's changing

Previously, there was no ceiling on how many webhook subscriptions could be created per customer. That opened the door to two common problems:

• Accidental overload — A developer iterating quickly on an integration could unknowingly create hundreds of duplicate subscriptions without realizing it, silently degrading performance.
• Automated proliferation — some tools auto-generate webhook subscriptions, and without a limit, those can stack up fast.
• Malicious abuse — In the worst case, a bad actor could flood the system with thousands of subscriptions and impact Swapcard's performance for everyone.

How it works

The fix is simple: 20 webhook subscriptions per event, maximum.

• If a customer already has 20 active subscriptions, any attempt to create a new one will be blocked with a clear error message.
• Existing subscriptions are unaffected — the limit applies to new creations going forward.
• The cap applies across all webhook events and endpoints for that customer account.

Why this matters

This isn't just a defensive measure — it's a reliability investment for every team building on Swapcard's API. Clean integrations perform better, are easier to debug, and don't silently eat up system resources in the background.

💡 Pro tip: If you're regularly hitting or approaching the 20-subscription limit per event, audit your active webhooks for duplicates or stale endpoints. A lean webhook setup is a healthy one.