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 Client Data Encryption Key API

Issues a client data encryption key used to encrypt sensitive fields (for example, account numbers and tax IDs) in requests to other BMO open-banking APIs such as Account Validation. Published as a Swagger 2.0 definition.

BMO Client Data Encryption Key API is one of 11 APIs that BMO publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Security and Encryption. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 1 operation across 1 path, and defines 7 schemas. It is described by OpenAPI 2.0, at version 1.0.0.

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

1 operations 1 paths 7 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
1.0.0
Base URL
https://sandbox-open-api.bmo.com/open-banking/commercial-sb
Authentication
API Key
Resource Areas
1

Authentication & Security 1

BMO Client Data Encryption Key API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (api-key-1).

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

retrieveClientDataEncryptionKey 1
POST
/issued-device-administration/client-data-encryption-key/get
REST Utility framework to retrieve cryptographic instructions such as public Customer Management key (CMK) details, encryption method and algorithm etc based on a reource uri and key alias
post-retrievecryptoinstruction 11 params → 200400401403404415429500

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are OriginatorData (6 properties), key (5 properties), Result (4 properties), RetrieveClientKeyRequest (3 properties). Each schema is shown below with its type and property counts.

RetrieveClientKeyRequest
object
3 properties 2 required
OriginatorData
object
6 properties 2 required
Result
object
4 properties
ResultDetails
object
2 properties
exceptionResult
object
1 property 1 required
key
object
5 properties 1 required
RetrieveClientKeyResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bmo-client-data-encryption-key-swagger.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 Wire Payments (Canada) API
BMO EFT Payments API
BMO Instant Payments (Interac) API
BMO Image Retrieval API
BMO Authorize & Token API
BMO Push Notification API
Where this information came from

This is an independent, third-party profile of BMO Client Data Encryption Key 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.