During the open Beta, limits are set per organization. New organizations start with the defaults below.
Orbimon is in open Beta. These limits may change before general availability, and we can adjust them for your organization depending on your use case. After the Beta, we will offer plans with different limits. If you need different limits, contact us.
API request usage is shown in the dashboard. The monthly API request limit is not enforced yet. Ingest rate limits apply and return 429 when exceeded.
Organization limits
| Limit | Default |
|---|---|
| Data interval (Edge uploads) | Every 5 minutes |
| API requests per month | 100,000 |
| Monitors | 2 |
| Members (pending invitations count) | 2 |
Your organization’s current values are on the Billing page in the dashboard.
What counts toward the monthly request limit
Counted toward the monthly limit:
- Edge uploads and checks
- API calls with user or service tokens
- Dashboard (app) usage
- Anonymous reads of your organization's public share links (shown under Public shares on the API usage breakdown)
Recorded but not counted:
- Sign in or token failures (
401) - Server errors (
5xx) - Responses served from the read cache
403 and 429 responses count toward the monthly total. The monthly API request cap is not enforced yet. Ingest 429 responses mean you exceeded your allowed upload rate for that window.
Edge uploads and the monthly limit
At a 5 minute upload interval, one Edge sends about 8,640 ingest requests in a 30 day month (about 43,200 at a 1 minute interval). Two Edges at 5 minutes use about 17,280 of 100,000 monthly requests.
Caching and data freshness
Monitor data only changes when your Orbimon Edge uploads a new batch, once per upload interval. The API keeps each computed monitor data response for your organization and serves it again until the next upload can arrive, so data is at most about one upload interval old. Polling more often than your upload interval returns the same data; poll at your upload interval or slower.
Usage in the dashboard updates every few minutes, so the latest requests may not show yet.
Cached data is private to your organization. Responses are never marked public, any Cache-Control they carry is private, and they include Vary: Cookie, Authorization, so shared caches and proxies never store them.
Monitor and monitor data responses carry the X-Orbimon-Cache header:
| Value | Meaning |
|---|---|
hit | Served from the cache, at most one upload interval old |
miss | Computed for this request and kept for later requests in the same interval |
bypass | Computed for this request and not kept, for example when the cache was unavailable or the response was too large |
Browsers can read this header on cross-origin requests. Historical ranges that are fully in the past, such as obstruction map history ending more than an hour ago, may be kept for up to one hour.
The monthly usage endpoint GET /v1/organizations/:org_id/usage uses Cache-Control: private, max-age=60 so repeat dashboard loads stay fresh without bypassing shared caches.
Rate limiting
When ingest exceeds your organization’s allowed rate, the API returns 429 with JSON:
code:RATE_LIMITEDretry_after: seconds to waitsend_interval_secondsandconfig_version
The response includes Retry-After and X-Orbimon-Config-Version. Back off and retry after retry_after seconds. See Edge API.
Query limits
The dashboard chart picker uses fixed windows. The HTTP API limits how wide a range you can request per resolution (for example raw metrics up to 12 hours). See Monitors and data and Monitors API.
Retention
Telemetry and event retention are described in Concepts.