How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

BMO Wire Payments (Canada) API

Submits and tracks Canadian domestic and international wire payments from BMO business accounts, secured with OAuth 2.0 and a client API key.

BMO Wire Payments (Canada) API is one of 11 APIs that BMO publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments, Wire Transfer, and Canada. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 2 operations across 2 paths, organized into 2 resource areas, and defines 5 schemas. It is described by OpenAPI 3.0.3, at version 1.0.2.

Requests are made against a single base URL, https://sandbox-open-api.bmo.com/open-banking/commercial-sb.

2 operations 2 paths 5 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.2
Base URL
https://sandbox-open-api.bmo.com/open-banking/commercial-sb
Authentication
API Key, OAuth 2.0
Resource Areas
2

Authentication & Security 2

BMO Wire Payments (Canada) API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-api-key (api-key-1). It supports OAuth 2.0 (OAuth) using the authorizationCode flow, exposing 3 scopes.

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 POST. They span 2 resource areas: SendPayment, GetPaymentStatus. Each is listed below with its method, path, parameters, and response codes.

SendPayment 1

Receive wire payment request in PAIN.001 ISO from BMO Canada partners/customers to initiate wire payment and send acknowledgement as response in PAIN.002 ISO.

POST
/tpp/wires/payment-initiation/customer-credit-transfer-initiation
Send Wire Payment
TppCustomerCreditTransferInitiation 13 params body → 200400401403404415429500
GetPaymentStatus 1

Receive payment inquiry request in CAMT.005 ISO from BMO Canada Partners/Customers and send payment status as response in PAIN.002 ISO.

POST
/tpp/wires/payment-initiation/get-transaction-status/get
Obtain Payment Status
TppGetPaymentStatus 13 params body → 200400401403404415429500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Problem (5 properties), SECURE (2 properties), CustomerPaymentStatusReportResponse (1 property), GetTransactionRequest (1 property). Each schema is shown below with its type and property counts.

Problem
object
5 properties
CustomerCreditTransferInitiationRequest
object
1 property 1 required
GetTransactionRequest
object
1 property 1 required
CustomerPaymentStatusReportResponse
object
1 property 1 required
SECURE
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bmo-wire-payments-ca-openapi.json Raw ↑

Other APIs BMO publishes across the network.

BMO Account Validation API
BMO Account Information API
BMO ACH Payments API
BMO Wire Payments (U.S.) API
BMO EFT Payments API
BMO Instant Payments (Interac) API
BMO Image Retrieval API
BMO Authorize & Token API
BMO Client Data Encryption Key API
BMO Push Notification API
Where this information came from

This is an independent, third-party profile of BMO Wire Payments (Canada) API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.