KeyBank Wire Inquiry API
The Wire Inquiry API tracks the status and delivery of wire transfers associated with commercial KeyBank accounts. It exposes operations to list wire transactions, retrieve detailed information for a specific wire by transaction id, and a health check, giving treasury teams real-time visibility into outbound and inbound wire activity for reconciliation. Authenticated with OAuth2 bearer tokens and mutual TLS client certificates over https://partner-api.key.com, with a QV sandbox for integration testing.
KeyBank Wire Inquiry API is one of 10 APIs that KeyCorp publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Inquiry, Wire Transfer, Reporting, and United States. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 3 operations across 3 paths, organized into 2 resource areas, and defines 18 schemas. It is described by OpenAPI 3.1.0, at version 1.3.6.
Requests are made against 2 base URLs: https://partner-api-qv.key.com, https://partner-api.key.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
KeyBank Wire Inquiry API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (bearerAuth).
By default, every request must be authenticated.
bearerAuth— Access token supplied in the Authorization header using the Bearer scheme (e.g. Authorization: Bearer {token}).
Paths & Operations 3
Across 3 paths, the API surfaces 3 operations — 2 GET, 1 POST. They span 2 resource areas: HealthCheck, Wire. Each is listed below with its method, path, parameters, and response codes.
Verify you can connect to the API service.
Wire Inquiry functions to list wires and retrieve wire details
Schemas 18
The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are WireDetailTransaction (27 properties), WireListTransaction (13 properties), PostalAddress (10 properties), Exception (6 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from KeyCorp 9
Other APIs KeyCorp publishes across the network.