Skip to content

Rate limits ​

Limits are applied per workspace and per X-Client-Name:

limits
Sustained60 requests per minute
Burstup to 20 requests in one second
Over the limit429 Too Many Requests with a Retry-After header

Good habits ​

  • Retry with backoff. On 429 wait Retry-After seconds. On 5xx, retry idempotent requests (GET, PUT, DELETE) with exponential backoff and jitter.
  • Batch writes. POST .../scheduled-visits accepts a whole route in one call: one request for 50 visits, not 50 requests.
  • Page with the maximum size (size=200) when reading full collections.
  • Cache what rarely changes, such as chains, brands and survey fields.
  • Sync incrementally with since instead of re-reading everything.

HTTP methods ​

HTTP methods
GETRead
POSTCreate
PUTReplace (v1)
PATCHUpdate only the fields you send (v3)
DELETEDelete. Never takes a body; IDs go in the path or query string.