UP42 · Rate Limits

Up42 Rate Limits

UP42 does not publish fixed numeric per-endpoint rate limits for the REST API. The practical governor on usage is the prepaid credit balance and, for enterprise accounts, budgets that cap credit spend rather than a per-minute request cap. Access tokens are short-lived (about 5 minutes), so clients must refresh tokens frequently and cache them for their lifetime. Long-running operations (tasking acquisitions, large orders, processing jobs) are asynchronous - clients poll order/job status or subscribe to webhooks rather than holding open a request. Callers should implement backoff on 429 responses.

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

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

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

Tagged areas include Geospatial, Earth Observation, Satellite Imagery, Rate Limiting, and Quotas.

4 Limits Throttle: 429
GeospatialEarth ObservationSatellite ImageryRate LimitingQuotas

Limits

REST API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the api.up42.com REST API.
Credit Balance account
credits
prepaid balance
Effective quota on orders/processing is the prepaid credit balance (100 credits = 1 EUR).
Enterprise Budgets workspace
credits
per budget
Enterprise accounts can define budgets that cap credit spend per workspace.
Access Token Lifetime token
seconds
~300
Access tokens are valid for roughly 5 minutes and must be refreshed.

Policies

Token Refresh
Cache the OAuth2 access token for its ~5 minute lifetime and refresh before expiry rather than requesting a new token per call.
Asynchronous Polling
Tasking, ordering, and processing are asynchronous; poll order/job status or use webhooks instead of blocking on a single request.
Backoff Strategy
Implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources