FAQs

Use your KeyBank credentials to get an access token. Run the following cURL command. The certificate files must be identified in the first line. Application credentials are Base64 encoded and used with your client credentials to get an access token.

curl -X POST --cert {{client.crt}} --key {{client.key}} --cacert {{ca.crt}} \ 'https://{{HOST}}/oauth/v1/token' \
-H 'Authorization: Basic {{base64(CONSUMER_KEY:CONSUMER_SECRET)}}' \
-H 'Content-Type: application/x-www-formurlencoded' \
-H 'X-CorrelationId: {{transaction identifier at overall system level}}' \
-d 'Id={{CLIENT_ID}}&Key={{CLIENT_SECRET}}&grant_type=client_credentials'

Most likely, you are correctly authenticated to access our APIs, but do not have authorization for the API product you are trying to use. There is a good way to figure this out.

1. Review your token response and look at the api_product_list_json field. This lists which APIs you have access to. If you don’t see the API listed, use our Client Support form to request this API product.
2. Verify system security settings.
   • Make sure your IP addresses are correct. Sometimes IP addresses change with a proxy.
   • Confirm that your certificates are valid and saved in your trust store.
3. If you still get an error, reach out to the onboarding team to get information about your status and current products.

Connection to the KeyBank network requires a mutual TLS two-way authentication mechanism that uses digital certificates signed using the public key infrastructure (PKI) framework. Therefore, KeyBank requires a public certificate chain from the client that meets the following requirements:

• Only one certificate is required for all APIs.
• The certificate must have a CSR and private key.
• The certificate chain must include the root, intermediate, and leaf.
• The certificate can be in any format, like *.pem, *.crt, or *.cer.
• Certificates cannot be self-signed.
• The certificate must be issued by a trusted certificate authority organization like DigiCert.

In any situation, we aim to provide information in a timely and efficient manner, depending on the circumstance.

1. If there is a major upgrade approaching, we will provide notice and any client-action information 3+ weeks in advance. This communication will be shared via email and also available on our Announcements page.
2. For service interruptions due to operational maintenance, we typically give one-week notice in advance by email as well as on the Developer Portal banner.
3. In the event of an emergency downtime, the notice period will be shorter. An email will be sent out to clients immediately, with the Developer Portal banner and possible related content to be updated soon after.

Use the Client Support form to submit an issue. There is a text field in the form that will allow you to paste the cURL command used or the request body text. However, this field is limited. Once a Support member has contacted you, reply to the secure email with the following information:

• Complete cURL command.
• Screenshot or text file of the URL path and header parameters used in your API tool, like Postman.
• Screenshot or text file of the request and response payloads.

All information should be shared securely through trust and encrypted communication channels. If this is an urgent or immediate matter, use this email for emergency request….