Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.getasset.com/llms.txt

Use this file to discover all available pages before exploring further.

Asset applies rate limits to API requests to ensure reliable performance across our Platform. Rate limits protect the system from sudden spikes in traffic, ensuring consistent availability and response times for everyone.

​
Request Limits

Asset enforces the following API rate limits:
  • Tenant-level requests: 300 requests per minute
  • Business-level requests: 300 requests per minute
Limits are applied independently at the Tenant and Business levels, preventing heavy usage in one area from affecting others.

​
API Response Headers

Every API response includes headers to help you monitor your usage and stay within rate limits:
HeaderDescription
x-ratelimit-limitThe maximum number of requests permitted per minute.
x-ratelimit-remainingThe number of requests remaining in the current time window.
x-ratelimit-resetThe time (in UNIX timestamp format) when the rate limit resets.
Using these headers, your application can manage its request patterns.

​
Exceeding Rate Limits

If you exceed these limits, Asset APIs return:
  • HTTP status code: 429 Too Many Requests
The response body will include a clear message indicating you’ve reached your limit.

​
Managing Your Requests

To ensure optimal performance and avoid exceeding rate limits, we recommend:
  • Monitoring the rate-limit headers returned with each response to proactively manage your usage.
  • Implementing retry mechanisms with exponential backoff.
  • Spacing requests evenly and batching API calls whenever possible.
If you have questions or anticipate higher usage needs, contact Asset support—we’re here to help.
Questions? Reach out via our Contact form.