Scotiabank
Scotiabank is one of Canada's leading financial institutions and a major international bank. Through its Scotia TranXact developer portal, Scotiabank provides APIs for corporate and commercial customers to integrate banking capabilities into their treasury management, ERP, and CRM systems. APIs cover wire payments, real-time payments via INTERAC e-Transfer, EFT payments, account balance and transaction data, account validation, and payment track and trace.
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 Scotiabank the way a machine reads it — 43 machine-readable artifacts across 13 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 — Scotiabank scores 48.2/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Scotiabank
Each block below is one kind of artifact we hold for Scotiabank. 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 13
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.
Wire Payments API
Enables businesses to initiate secure, one-time wire transfers between accounts in the same currency (CAD or USD), domestically within Canada and the U.S., or internationally. U...
Real-time Payments API
Provides fast payment capabilities for business transactions via INTERAC e-Transfer for business. Customers can send up to $25,000 per transaction in real time.
EFT Payment API
Supports creation and submission of Electronic Funds Transfers (EFTs), including inquiring on payment and file status, deleting, updating, and recalling or reversing payments.
Account Balance and Transactions API
Provides the ability to retrieve account balance for the current day or any prior day along with enriched transaction data for the two years prior, and view a list of eligible d...
Account Validation API
Assists clients in determining the validity of an account number's format and indicates the likelihood of account ownership match for Scotiabank accounts.
Payment Track and Trace API
Provides the capability to inquire on the status of wire payments using unique reference numbers, offering real-time payment tracking powered by SWIFT GPI.
Scotiabank Account Validation API
The Account Validation API from Scotiabank — 1 operation(s) for account validation.
Scotiabank Accounts API
The Accounts API from Scotiabank — 3 operation(s) for accounts.
Scotiabank EFT Payments API
The EFT Payments API from Scotiabank — 2 operation(s) for eft payments.
Scotiabank Payment Tracking API
The Payment Tracking API from Scotiabank — 1 operation(s) for payment tracking.
Scotiabank Real-Time Payments API
The Real-Time Payments API from Scotiabank — 1 operation(s) for real-time payments.
Scotiabank Request for Payment API
The Request for Payment API from Scotiabank — 1 operation(s) for request for payment.
Scotiabank Wire Payments API
The Wire Payments API from Scotiabank — 2 operation(s) for wire payments.
Scroll within the panel for all 13 ·
Open Collections 1
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).
Scotiabank Scotia TranXact APIs
OPEN COLLECTIONPricing 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.
Scotiabank 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.
Scotiabank 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.
Scotiabank 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.
Scotiabank API Rules
SPECTRALScotiabank API Rules
SPECTRALJSON Schema 16
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.
Account
JSON SCHEMAAccountBalanceResponse
JSON SCHEMAAccountsListResponse
JSON SCHEMAAccountValidationRequest
JSON SCHEMAAccountValidationResponse
JSON SCHEMAEFTPaymentRequest
JSON SCHEMAEFTPaymentResponse
JSON SCHEMAPaymentTrackingResponse
JSON SCHEMARealtimePaymentRequest
JSON SCHEMARealtimePaymentResponse
JSON SCHEMARequestForPaymentRequest
JSON SCHEMARequestForPaymentResponse
JSON SCHEMAScotiabank Transaction
JSON SCHEMATransactionsListResponse
JSON SCHEMAWirePaymentRequest
JSON SCHEMAWirePaymentResponse
JSON SCHEMAScroll within the panel for all 16 ·
JSON Structure 2
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.
Scotiabank Structure
JSON STRUCTUREScotiabank Wire Payment Structure
JSON STRUCTUREExamples 1
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.
Security 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 Scotiabank — 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.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/scotiabank · machine-readable index on apis.io