Glossary

Explore Meshline

Products Pricing Blog Support Log In

Ready to map the first workflow?

Book a Demo

Glossary / Evaluation and implementation guide

Connector Rate Limits

Connector rate limits cap how many API requests can be made per unit of time — per second or per minute — regardless of total quota.

They are usually set by the upstream system being integrated (a CRM's API, for instance), and a good connector respects them with queuing and backoff rather than failing.

Rate limits shape sync throughput: how long a bulk import or a burst of updates takes.

A practical example

Example: your CRM allows 200 requests per minute. Importing 10,000 contacts with several calls each cannot finish in minutes; the connector must queue, pace itself, and the import realistically spans hours.

What to evaluate before investing

  • Ask which side sets the limit — the vendor's platform or the upstream system — and whether the connector adapts automatically.
  • Test a bulk operation of realistic size and measure wall-clock time, not just success.
  • Check whether the connector queues and paces requests transparently, or surfaces rate-limit errors for your team to handle.

Limitations and tradeoffs

Rate limits are often outside the vendor's control, so promises of "unlimited sync speed" should be read against the upstream system's documented limits. Slow upstream limits can dominate your real throughput.

Plan your next step with MeshLine

Connect this decision to your automation, organic marketing and customer lifecycle management. In a MeshLine demo, discuss your existing tools, the scope you need and how to measure the result.