TD Bank
TD Bank, N.A. (America's Most Convenient Bank) is the U.S. retail and commercial subsidiary of Toronto-Dominion Bank, serving more than 10 million customers from Maine to Florida through roughly 1,100 branches. TD's Open Banking developer portal (hosted at developer.td.com / openbanking.amcb.developer.td.com) exposes an FDX-aligned API suite — Account Basic, Account Detailed, Customer, Transactions, Statements, Tax Forms, Bill Payment, Rewards — plus Consent, Token, Service Token, Apps Management, and Notifications utility APIs that are operated for vetted fintechs and data aggregators via the Akoya Data Access Network. TD also exposes TD Online Mart Recurring Payment APIs through its US/Canadian Merchant Solutions (Worldline-backed).
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles TD Bank the way a machine reads it — 50 machine-readable artifacts across 16 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — TD Bank scores 57.9/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile TD Bank
Each block below is one kind of artifact we hold for TD Bank. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 16
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
TD Bank Transactions API
FDX v6.2 Transactions endpoint that returns posted and pending transaction data for a consented account — amounts, dates, descriptions, merchant fields, status — with support fo...
TD Bank Statements API
FDX v6.2 Statements endpoint that lists available statement periods for a consented account and lets consumers retrieve the statement PDF. Supports the standard FDX statement me...
TD Bank Tax Forms API
FDX v6.2 Tax Forms endpoint that lists tax forms (e.g. 1099-INT, 1099-DIV) issued for a consented TD account in a given year and lets consumers retrieve the form PDF.
TD Bank Rewards API
TD Open Banking Rewards API v1.0.0 returns reward program and membership information for the currently authenticated user — designed to track rewards participation across travel...
TD Bank Notifications API
Notifications API — retrieves alerts about significant changes on the TD/Akoya network, including planned/unplanned maintenance outages and consent events (revoked or modified c...
TD Online Mart Recurring Payment API
TD Merchant Solutions Recurring Payment API (Worldline-backed gateway) — lets merchants schedule and process recurring membership / subscription card payments. Supports API Pass...
TD Bank Accounts API
The Accounts API from TD Bank — 3 operation(s) for accounts.
TD Bank Apps API
The Apps API from TD Bank — 2 operation(s) for apps.
TD Bank Bill Payments API
The Bill Payments API from TD Bank — 1 operation(s) for bill payments.
TD Bank Clusters API
The Clusters API from TD Bank — 2 operation(s) for clusters.
TD Bank Consents API
The Consents API from TD Bank — 2 operation(s) for consents.
TD Bank Customers API
The Customers API from TD Bank — 2 operation(s) for customers.
TD Bank Payees API
The Payees API from TD Bank — 1 operation(s) for payees.
TD Bank Service Tokens API
The Service Tokens API from TD Bank — 1 operation(s) for service tokens.
TD Bank Subscriptions API
The Subscriptions API from TD Bank — 1 operation(s) for subscriptions.
TD Bank Tokens API
The Tokens API from TD Bank — 3 operation(s) for tokens.
Scroll within the panel for all 16 ·
Open Collections 13
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
TD Bank Account Basic API
OPEN COLLECTIONTD Bank Account Detailed API
OPEN COLLECTIONTD Bank Apps Management API
OPEN COLLECTIONTD Bank Bill Payment API
OPEN COLLECTIONTD Bank Consent API
OPEN COLLECTIONTD Bank Customer API
OPEN COLLECTIONTD Bank Notifications API
OPEN COLLECTIONTD Bank Rewards API
OPEN COLLECTIONTD Bank Service Token API
OPEN COLLECTIONTD Bank Statements API
OPEN COLLECTIONTD Bank Tax Forms API
OPEN COLLECTIONTD Bank Token API
OPEN COLLECTIONTD Bank Transactions API
OPEN COLLECTIONScroll within the panel for all 13 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Td Bank Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Td Bank Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Td Bank Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
TD Bank API Rules
SPECTRALTD Bank API Rules
SPECTRALJSON Schema 4
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
TD Bank FDX Account
JSON SCHEMATD Bank FDX Consent
JSON SCHEMATD Bank FDX Customer
JSON SCHEMATD Bank FDX Transaction
JSON SCHEMAJSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Td Bank Account Structure
JSON STRUCTUREExamples 6
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Td Bank Account Example
EXAMPLETd Bank Consent Example
EXAMPLETd Bank Customer Example
EXAMPLETd Bank Notification Example
EXAMPLETd Bank Token Example
EXAMPLETd Bank Transaction Example
EXAMPLESecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for TD Bank — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 7
Properties that don't map to a standard resource type
Scroll within the panel for all 7 ·
← All providers · Data indexed from github.com/api-evangelist/td-bank · machine-readable index on apis.io