Raum Network
Raum Network API Rate Limits
Rate-limit convention for Raum Network API clients, including RFC RateLimit headers, Retry-After, and recovery behavior.
About this page
Raum Network catalog API uses a 60-request rolling client window of 60 seconds per deployment instance. Responses expose RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, and RateLimit-Policy: 60;w=60. A request over quota receives HTTP 429, JSON error code rate_limit_exceeded, and Retry-After in seconds. Agents should stop sending requests when RateLimit-Remaining reaches zero, wait for RateLimit-Reset or Retry-After, then retry with bounded backoff. Limits may change by API version; clients must read response headers instead of hard-coding quota assumptions.
Topics
- RateLimit-Limit
- RateLimit-Remaining
- RateLimit-Reset
- Retry-After
- HTTP 429