Terminology

• Passthrough request: These requests are sent directly to the integration's API and follow each integration's specific API formats instead of Merge's unified format.

• Rate limit: Typically used to control the rate of requests sent and/or received.

Why does my linked account hit rate limits more frequently when I use passthrough requests?

Some third-party providers limit the number of simultaneous sync tasks.

Sending passthrough requests during an active sync makes hitting rate limits more likely.

Merge applies integration-specific rate limits to all API requests sent to third-party providers. These limits include both Merge syncs and any passthrough requests you make. Passthrough requests count toward the same limits as syncs, so we recommend avoiding passthrough requests while a sync is running. Otherwise, you may reach the rate limit, which can cause your syncs or passthrough requests to fail.

What should I do if I hit rate limits?

1. Avoid passthrough requests during active sync windows to reduce the chance of exceeding rate limits.

2. Use exponential backoff in your retry logic: Start with a 1-minute delay and increase the delay with each retry.

3. Request an exemption if critical: We can disable integration-specific limits for your organization. Note: This increases the risk of hitting hard third-party rate limits, which could cause sync failures.

4. For more real-world examples and tips on handling rate limits, check out our REST API rate limiting guide.