TD Bank · Rate Limits

Td Bank Rate Limits

TD Bank's Open Banking developer portal does not publish numeric per-second / per-minute rate limits. Access is partner-gated via OAuth 2.0 with Pushed Authorization Request (PAR) and is bounded by FDX consent and Akoya onboarding agreements. Throttling and quotas are governed by the partner-app configuration. Customer consent revocation is the ultimate rate-limiting mechanism — a revoked consent immediately blocks Data API access for that resource.

Td Bank Rate Limits is the machine-readable rate-limit profile for TD Bank on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring varies.

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

Tagged areas include Rate Limiting, Banking, FDX, and Akoya.

5 Limits Throttle: 429
Rate LimitingBankingFDXAkoya

Limits

FDX Data APIs (Account Basic/Detailed, Customer, Transactions, Statements, Tax Forms, Bill Payment, Rewards) oauth_client
varies
see Akoya partner agreement
Consent API oauth_client
varies
see Akoya partner agreement
Token / Service Token APIs oauth_client
varies
see Akoya partner agreement
Apps Management API v2 service_token
varies
see Akoya partner agreement
Notifications API service_token
varies
see Akoya partner agreement

Policies

OAuth 2.0 with PAR
Every Data API call requires an OAuth 2.0 access token obtained via the Pushed Authorization Request flow; utility APIs use client_credentials Service Tokens.
FDX Consent Gating
Every Data API resource is gated by an active FDX consent. Revoked or expired consents immediately produce 401/403.
Backoff Strategy
Use exponential backoff with jitter on 429/503; honor Retry-After when present.
Notifications-Driven Backoff
Subscribe to the Notifications API for maintenance and consent_revoked events; reduce polling during announced maintenance windows.

Sources