KeyBank Wire Transfer API
The Wire Transfer API, delivered through KeyBank's combined RTP and Wire Payments service, facilitates high-value domestic wire payments from commercial accounts. It provides operations to initiate a payment, validate payment details before submission, and look up RTP/wire network participants by routing number. Requests are authenticated with OAuth2 bearer tokens and mutual TLS client certificates and carry an x-fapi-interaction-id header; production runs on https://partner-api.key.com with a QV sandbox.
KeyBank Wire Transfer API is one of 10 APIs that KeyCorp publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Payments, Wire Transfer, Commercial Banking, and United States. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 5 operations across 5 paths, organized into 4 resource areas, and defines 13 schemas. It is described by OpenAPI 3.0.2, at version 1.3.3.
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 Transfer API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (bearerAuth).
Paths & Operations 5
Across 5 paths, the API surfaces 5 operations — 3 GET, 2 POST. They span 4 resource areas: HealthCheck, Initiate, Participant, Validate. Each is listed below with its method, path, parameters, and response codes.
Verify you can connect to the API service. A bearer token is required.
Send a payment.
Look up a RTP participating banks.
Perform validation checks for a payment transaction.
Schemas 13
The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are paymentTransactionRequestV1 (21 properties), paymentTransactionResponse (13 properties), serviceErrorData (10 properties), party (7 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.