Our process

Glossary

A

API

An Application Programming Interface (API) is a software program that connects two applications. APIs are code that helps different systems to communicate and exchange data easily using reusable software building blocks.

API Marketplace

A space within Chase Developer where you can publish and discover APIs. Chase Developer is a constantly growing space; once you join you'll have access to an ever-growing list of Chase API products and solutions.

C

Catalog

The complete list of available APIs and solutions. You can browse our ever-growing catalog even if you don't have login access to the API Marketplace.

Chase Digital API call

A request to your API. Once the API receives the call, it processes it and sends a response.

Chase Digital API Gateway

The services platform responsible for partner onboarding and registration for API usage. A partner is enabled, authenticated, authorized and published through the Chase Digital API Gateway.

D

Documentation

The instructions and details you need to integrate with the API. It's composed of technical documents that enable you to connect and utilize the product. Chase Developer documentation includes code samples, fixes for common issues and use cases for each individual API.

O

OAuth 2.0

The instructions and details you need to integrate with the API. It's composed of technical documents that enable you to connect and utilize the product. Chase Developer documentation includes code samples, fixes for common issues and use cases for each individual API.

OAuth Access Token

A string requested in the token call using Digital API Gateway credentials. The OAuth Access Token is valid for 60 minutes.

P

Playground

Also know as the "sandbox," this is place in Chase Developer where you can create, test, develop and adopt solutions custom made for your business. You can get access to the Chase Developer sandbox by creating an account.

S

Solution

A bundle of individual APIs working together to fulfill a use case. For example, the Pay with Points (PWP) solution: in practice it's composed of 4 different APIs, with one handling the enrollment of the Chase PWP feature, another checking the user's available points balance and another two handling the order and payment. There isn't a standalone, singular Pay with Points API, but these 4 bundled together create a solution enabling users to pay with Chase credit card points.

Specifications

Commonly also referred to as "Swagger", it's the framework and tools to help you custom-build and document your API.

T

Two-legged Authentication

A verification process between two parties. For purposes of this document, the two parties are the partner and Chase. The process is based on OAuth 2.0 standard protocol for authorization.

Y

YAML Files

Files written in Yet Another Markup Language (YAML) that contain a readable data serialization language, commonly used for configuration files. A YAML file is used in many applications where data is stored (e.g., debugging output) or transmitted (e.g., document headers). YAML targets many of the same communications applications as XML but has a minimal syntax. For our APIs, “YAMLfile” and “Swagger” are used interchangeably.

Ready to begin?

Connect with us to see what solutions work for you and how to become a partner.