Vantage · Rate Limits

Vantage Sh Rate Limits

Vantage applies per-token rate limiting to the public REST API and returns HTTP 429 when a client exceeds its allowance. Exact published numeric limits are not reconciled here; clients should read the standard rate-limit response headers Vantage returns and back off accordingly. Bulk cost retrieval is also bounded by pagination - the GET /costs endpoint returns a maximum of 5000 results per request and is paged via the limit and page parameters.

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

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

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

Tagged areas include Cloud Cost, FinOps, Cost Management, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Cloud CostFinOpsCost ManagementRate LimitingQuotas

Limits

REST API Requests token
requests
not published (per-token; 429 on exceed)
Vantage rate limits API requests per token and returns HTTP 429 when exceeded.
Costs Query Page Size request
results
5000
GET /costs returns at most 5000 results per request; page through with limit and page.
Cost Data Export account
exports
configurable
For large extracts use POST /costs/data_exports rather than paginating the costs endpoint.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor any Retry-After header on 429 responses.
Pagination
List endpoints are paginated; iterate with page and limit rather than requesting unbounded result sets.
Bulk Export
Prefer the data-export endpoints for large cost datasets to avoid rate-limit pressure from deep pagination.

Sources