bitlync Docs

Concepts

Rate limits

We pace writes to the vendor’s real limit. If we have to wait, you get a rate-limit response (HTTP 429) with Retry-After. You do not guess a vendor quota.

One sync per MSP tenant fills the store. Every product on that tenant reads the same copy. When each product polls the same PSA, they share one budget.

Today — every product polls

ISV A ISV B ISV C ISV D ISV E PSA API shared budget Five products. Same reads. One noisy poll starves the MSP.

With Bitlync — one governed sync

ISV A ISV B ISV C ISV D ISV E bitlync store PSA one sync Store-served reads. Zero vendor calls. N products. Same one sync.

Mechanism

ISV-facing: 600 req/min times the number of connected MSPs. There is no daily cap. The per-minute rate is the limit. Hit it and you get a rate-limit response with Retry-After. There is no silent throttle.

What the caller sees

A rate-limit response you can branch on. The header is the wait. Do not treat a delayed 200 as a throttle.

Rate limit (429) + wait
HTTP 429
Retry-After: 12

{
  "status": 429
}

No silent queue that looks like success.

Quickstart Reference