IFTTT Webhooks API Transition: Unresolved Support for Batch Requests

Webhooks API Transition

IFTTT’s Webhooks service replaced the legacy Maker platform, requiring all applets to use a bearer token (API key) in the Authorization header for POST requests. The new endpoint enforces a rate limit of 100 requests per minute per key, returning a 429 status when exceeded.

Documentation makes no reference to batching or multi‑payload requests. Attempts to POST an array of payloads consistently return a 400 Bad Request, indicating that the API does not currently support batch processing.

For developers handling high‑frequency triggers, this limitation raises questions about how to maintain throughput while respecting the rate limit and whether alternative patterns can mitigate the issue.

• Will IFTTT introduce batch request support in future API releases?
• Is there a documented workaround or recommended pattern for sending multiple payloads in a single POST?
• Can the rate limit be increased for certain keys or use cases, or is a separate key required for high‑volume traffic?