Swoogo · Rate Limits

Swoogo Rate Limits

The Swoogo API enforces a credit-based rate limit rather than a fixed requests-per-second cap. Each API account is allotted 2000 credits in every rolling 10-minute period. Requests consume credits by operation type: retrieving a collection (a "get all" list request) costs 10 credits, while retrieving a single record costs 1 credit. When the credit allotment is exhausted, further requests are throttled until the window refreshes. Separately, OAuth2 bearer tokens expire every 30 minutes and must be re-requested from POST /api/v1/oauth2/token.

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

It captures 4 rate-limit definitions, measuring credits and minutes.

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

Tagged areas include Event Management, Event Registration, Rate Limiting, and Quotas.

4 Limits Throttle: 429
Event ManagementEvent RegistrationRate LimitingQuotas

Limits

Credit Allotment account
credits
2000 per 10 minutes
Rolling 10-minute window; credits refresh as the window advances.
List Request Cost account
credits
10 credits per request
Any "get all" collection request (e.g. GET /events, GET /registrants) costs 10 credits.
Single Record Cost account
credits
1 credit per request
Retrieving a single record (e.g. GET /events/{id}) costs 1 credit.
Token Lifetime token
minutes
30 minutes
OAuth2 bearer tokens expire every 30 minutes and must be re-issued.

Policies

Credit Budgeting
Prefer single-record fetches and pagination tuning over repeated full-collection pulls to conserve credits; a list request costs 10x a single-record request.
Token Refresh
Re-request a bearer token from /oauth2/token before the 30-minute expiry rather than assuming a token remains valid.
Backoff Strategy
On throttling (429), back off with exponential delay and jitter until the 10-minute credit window refreshes.

Sources