KeyCorp · Authentication Profile

Keycorp Authentication

Authentication

KeyCorp secures its APIs with http and mutualTLS across 2 declared security schemes, as derived from its OpenAPI definitions.

BankingCommercial BankingFinancial-ServicesFortune 500PaymentsUnited StatesSuper-Regional BankTreasury ManagementEmbedded BankingACHReal-Time PaymentsWire Transfer

Methods: http, mutualTLS Schemes: 2 OAuth flows: API key in:

Security Schemes

bearerAuth http

scheme: bearer

mutualTLS mutualTLS

Source

Authentication Profile

generated: '2026-06-20'
method: derived
source: openapi/ (KeyBank commercial-banking specs) + developer.key.com
summary:
  types:
  - http
  - mutualTLS
  http_schemes:
  - bearer
  bearer_formats:
  - JWT
  transport_security:
  - mutual-TLS (client certificate)
  additional_headers:
  - x-fapi-interaction-id
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  bearerFormat: JWT
  description: >-
    OAuth2-issued access token supplied in the `Authorization` header using the
    `Bearer` scheme (e.g. `Authorization: Bearer {token}`). Tokens are minted
    through KeyBank's partner OAuth flow (F5 APM); every commercial/embedded
    banking operation requires a valid bearer token.
  sources:
  - openapi/keycorp-account-validation-openapi.yml
  - openapi/keycorp-ach-inquiry-openapi.yml
  - openapi/keycorp-ach-originations-openapi.yml
  - openapi/keycorp-check-services-openapi.yml
  - openapi/keycorp-rtp-inquiry-openapi.yml
  - openapi/keycorp-rtp-wire-payments-openapi.yml
  - openapi/keycorp-wire-inquiry-openapi.yml
- name: mutualTLS
  type: mutualTLS
  description: >-
    In addition to the bearer token, all calls to https://partner-api.key.com
    (and the QV sandbox at https://partner-api-qv.key.com) are transport-secured
    with a KeyBank-issued mutual-TLS client certificate. Documented as a hard
    requirement across the KeyBank Developer Portal API catalog.
  sources:
  - https://developer.key.com/
extra:
  interaction_id:
    header: x-fapi-interaction-id
    format: UUID
    description: >-
      FAPI-style client-supplied correlation UUID required on request and echoed
      back on responses for end-to-end traceability. A malformed value returns
      "Required header 'x-fapi-interaction-id' is not valid."
  account_context:
    header: secondaryId
    description: >-
      KeyBank-issued secondary identifier required by Account Validation and
      certain reporting operations to scope the caller to a client relationship.
notes: >-
  No OAuth2 securityScheme with scopes is declared in the specs — tokens are
  opaque-to-consumer bearer JWTs issued out of band, so there is no public OAuth
  scope surface to catalog (scopes/ is correctly skipped for this provider).

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This security artifact

curl "https://apis.io/api/v1/security/keycorp-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.