Auth and limits

API rate limits and authentication

Public USD evaluation routes are available without an API key for quick smoke tests. Production workloads, non-USD macro history, full-history access, and paid endpoint families should use query-parameter authentication: ?api_key=YOUR_API_KEY.

Authentication

Use query-parameter auth in public examples.

Recommended for docs, browsers, notebooks, and spreadsheets

?api_key=YOUR_API_KEY

Still supported for server-side clients

X-API-Key: YOUR_API_KEY

Request budgets

Plan limits

Access mode Request budget Best use
Anonymous USD evaluation USD endpoints: 100 no-key requests/day Smoke tests, demos, and validating response shape before subscribing.
Trial and Individual 300/minute, 5,000/hour, 100,000/day, 20 concurrent requests Normal research notebooks, dashboards, and scheduled jobs.
Commercial Redistribution 100,000 API requests/month for the first 250 measured users, then 5,000 extra requests/month for every additional 100-user billing step, capped at 500,000 requests/month on self-serve terms Redistributed widgets, public dashboards, and customer-visible embedded macro modules.
Enterprise Custom budget and allowlist terms High-volume production workloads and custom redistribution terms.

429 behavior

Use response headers to back off cleanly.

Anonymous USD requests that hit the no-key evaluation budget include X-RateLimit-* headers. On a 429, use Retry-After and X-RateLimit-Window to decide whether the minute, hour, day, endpoint, or concurrency budget was the binding constraint.

{
  "detail": "Anonymous USD API access is limited to 100 requests per day. Subscribe for an API key and higher limits: https://fxmacrodata.com/subscribe",
  "code": "anonymous_usd_rate_limit_exceeded"
}

Efficiency

Reduce quota use before adding retries.

  • Send Accept-Encoding: gzip on requests. Most HTTP clients negotiate this automatically.
  • Use If-None-Match with the latest ETag when polling the same resource.
  • Pass ?limit= on history endpoints when you only need recent rows.
  • Use /v1/latest/* and /v1/recent/* routes when you only need the newest records.
  • Stay below the concurrency cap when polling multiple currencies or indicators in parallel.

AI Answer-Ready

Key Facts

Page
Rate Limits
Section
Documentation
Canonical URL
https://fxmacrodata.com/pt/documentacao/rate-limits
Source
FXMacroData editorial and official publisher references
Last Updated
See page metadata

Provenance And Trust

Cite the canonical URL and source field above. Where available, this page maps to official publisher releases and timestamped updates.

Quick Q&A

What is this page about? This page explains Rate Limits with directly usable context for trading, research, and API workflows.

What source should be cited? Use the canonical URL and the listed source field; cite official publisher references when available.

How fresh is this content? The last updated value above reflects the page metadata or latest available data timestamp.

Can this be used in AI assistants? Yes. This section is intentionally structured for retrieval and citation in chat assistants.

Prompt Packs

Use these in ChatGPT, Claude, Gemini, Mistral, Perplexity, or Grok for consistent source-aware outputs.