Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.teal.dev/llms.txt

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

The Teal API uses rate limiting as a way to protect against bursts of incoming traffic to improve stability. Clients will recieve a 429 status response when rate limits are exceeded. In general, the API is rate-limited as follows:
  • All platform-level requests have a combined rate limit of 120 requests/minute.
  • All instance-level requests have a combined rate limit of 320 requests/minute.
In addition, the Refresh Ledger Transactions endpoint has an additional rate limit of 2 requests/minute. Every API response is accompained with the standard rate limiting headers. Use these values to gauge how many requests can be made before reaching the limit. For example, the headers below indicate that you can make 10 requests total, and only 4 additional requests can be made before reaching the limit. 
x-ratelimit-limit: 10
x-ratelimit-remaining: 4
x-ratelimit-reset: 1705624727
retry-after: 60
When you see a HTTP Status Code 429, wait 60 seconds before retrying the request. If you suddently see a increase number of rate limit responses, please contact us for help.