Department Of The Treasury Rate Limits

Treasury APIs split into two regimes. Fiscal Data and SAM.gov Entity Management are fronted by api.data.gov, which enforces a default 1,000-requests-per-hour limit per developer key (raisable via support). OFAC's Sanctions List Service and TreasuryDirect open feeds are unauthenticated and bounded by fair-use rather than per-key quotas. api.data.gov surfaces 429 with X-RateLimit-* headers; OFAC and TreasuryDirect use standard server throttling.

Department Of The Treasury Rate Limits is the machine-readable rate-limit profile for Department of the Treasury on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, across the api-data-gov and open tiers, measuring requests_per_hour and requests_per_minute.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, serviceUnavailable, and forbidden.

Tagged areas include Federal Government, Finance, Sanctions, Open Data, and Rate Limiting.

3 Limits Throttle: 429 Quota: 429
Federal GovernmentFinanceSanctionsOpen DataRate Limiting

Limits

api.data.gov default per-key limit api-key
requests_per_hour · hour
1000
api.data.gov increased limit (raise via support) api-key
requests_per_hour
higher; request via api.data.gov support
OFAC SLS / TreasuryDirect / IRS Fair-Use Throttle IP
requests_per_minute
fair-use; not published

Policies

api.data.gov Key Pattern
Fiscal Data and SAM.gov enforce limits at the api.data.gov gateway; excess returns 429. Increases must be requested via api.data.gov support.
OFAC SLS Bulk Pattern
OFAC publishes daily refreshed lists; consumers should download once per day rather than poll. Fair-use limits apply at the network edge.
Backoff Strategy
On 429 / 503 implement exponential backoff with jitter, honoring Retry-After when present.
Caching Encouragement
Fiscal Data datasets are stable on a daily-or-weekly cadence; cache results aggressively to reduce gateway load.

Sources