Swarmia · Rate Limits

Swarmia Rate Limits

Swarmia's REST API is authenticated with per-organization Bearer API tokens and intended for periodic export, ingestion, and management workflows rather than high-frequency real-time traffic. Swarmia does not publish specific numeric request-per-minute or request-per-day quotas in its public API documentation; clients should treat the API as rate-limited and back off on throttling responses. Specific limits are not reconciled in this artifact.

Swarmia Rate Limits is the machine-readable rate-limit profile for Swarmia on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests and timeframe.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Engineering Effectiveness, Developer Productivity, Analytics, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Engineering EffectivenessDeveloper ProductivityAnalyticsRate LimitingQuotasThrottling

Limits

Requests Per Minute (RPM) token
requests
see provider documentation
No public numeric RPM published; treat as rate-limited and back off on 429.
Requests Per Day (RPD) token
requests
see provider documentation
No public numeric RPD published.
Report Window request
timeframe
default last 7 days (UTC) when timeframe omitted
Bounds the data range returned by report endpoints unless startDate/endDate set.

Policies

Bearer Token Scoping
Tokens carry scopes (e.g. entityQuery for reports, aiUsage for ingestion); requests outside a token's scope are rejected.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources