Manova Rate limits
How many requests each API accepts, and the headers that tell you where you stand.
| API | Limit | Counted per |
|---|---|---|
Chat API (/chat/messages, /conversations, /usage) | 30 requests a minute | account |
Store API (/store/...) | 240 requests a minute | IP address |
| Order lookups (Manova → your store) | 6 an hour | conversation |
Every response carries the current budget:
X-RateLimit-Limit: 240
X-RateLimit-Remaining: 231Past the limit you get 429 with a Retry-After header, in seconds:
HTTP/1.1 429 Too Many Requests
Retry-After: 21
X-RateLimit-Limit: 240
X-RateLimit-Remaining: 0
{"code": "RATE_LIMITED", "message": "درخواستها زیاد شد؛ کمی بعد دوباره تلاش کن."}Staying under the limits
- Batch products. Send up to 100 per
POST /store/productsinstead of one per call. A full sync of 20,000 products is 200 calls, under a minute of budget. - Queue product updates. Collect changes for a few seconds and send them together, rather than one call per save.
- Stream, don't poll. A chat reply arrives on the same connection; there is nothing to poll.
Plans also have their own daily message limits and credits; those return 429 RATE_LIMITED or
402 INSUFFICIENT_CREDITS from POST /chat/messages.