HTTP 429Server

rate_limited

Too many requests - honor Retry-After header.

What this means

Your client has exceeded the per-key rate limit. The Retry-After response header tells you how many seconds to wait before retrying.

How to recover

Back off using Retry-After. Implement exponential backoff with jitter in your client.

Example response

All TetraFi errors include a stable code, a human-readable message, and a docs_url pointing to this page.

JSON

1{
2  "error": {
3    "code": "rate_limited",
4    "message": "Too many requests - honor Retry-After header.",
5    "docs_url": "https://tetrafi.io/docs/integration/errors/rate_limited/"
6  }
7}

7 linesjson

Match in code

TypeScript

1try {
2  await tetrafi.rfq.create({ /* ... */ });
3} catch (err) {
4  if (err.code === "rate_limited") {
5    // Back off using Retry-After. Implement exponential backoff with jitter in your client.
6  }
7  throw err;
8}

8 linestypescript

Related server errors

429

rate_limit_error

Too many requests - honor Retry-After header.

500

api_error

Internal server error - retry with exponential backoff.

503

maintenance

Scheduled maintenance - check status page.