Roadie · Rate Limits

Roadie Io Rate Limits

Roadie does not publish fixed numeric rate limits for its public REST API (https://api.roadie.so/api). Access is governed by tenant plan and by Roadie's permission model (RBAC) rather than by a documented per-minute request cap. The entity-push API is designed for idempotent, scheduled synchronization (recreating an entire entity set on a cron), which implicitly favors periodic batch calls over high-frequency requests. Clients should implement retries with exponential backoff and honor Retry-After on any 429 responses.

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

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

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

Tagged areas include Software Catalog, Internal Developer Portal, Backstage, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Software CatalogInternal Developer PortalBackstageRate LimitingQuotas

Limits

Public API Requests tenant
requests
not published
No fixed numeric request-rate limit is documented for the Roadie public API.
Entity Set Sync tenant
requests
not published
Entity sets are idempotent and intended to be re-pushed on a schedule rather than at high frequency.
Permission Model token
authorization
RBAC-governed
Access is bounded by the policies attached to the User or Service Token, not by a request quota.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Idempotent Sync
Prefer entity-set PUT for bulk catalog synchronization so repeated runs are safe and self-correcting.
Least Privilege
Use scoped Service Tokens for automation and grant only the RBAC policies each integration requires.

Sources