How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

JPMorgan Chase Connectivity API

Pay By Bank - Connectivity

JPMorgan Chase Connectivity API is one of 65 APIs that JPMorgan Chase publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Connectivity. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 1 operation across 1 path, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 2.0.8.

Requests are made against 4 base URLs: https://apigateway.jpmorgan.com/tsapi/paybybank/v2, https://apigatewayqaf.jpmorgan.com/tsapi/paybybank/v2, https://apigatewaycat.jpmorgan.com/tsapi/paybybank/v2, https://api-mock.payments.jpmorgan.com/tsapi/paybybank/v2.

1 operations 1 paths 9 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.8
Base URL
https://api.payments.jpmorgan.com/onboarding/v1
Resource Areas
1

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.

Connectivity 1

Pay By Bank - Connectivity

GET
/providers
List providers for a market
getProviders 1 param → 200

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are Provider (27 properties), Field (21 properties), SelectOption (3 properties), FinancialService (2 properties). Each schema is shown below with its type and property counts.

Provider
object
The provider model represents financial institutions with established connectivity with us. It specifies accesses to the financial institution, metadata about…
27 properties 18 required
HealthStatusValue
object
1 property
FinancialService
object
2 properties 2 required
Field
object
21 properties
SelectOption
object
3 properties
Providers
object
A representation of a collection of providers.
1 property 1 required
ImageUrls
object
Image urls of the provider
2 properties
Market
string
ISO 3166-1 alpha-2 country code for the market where the payment is initiated. - Market Coverage: DE, ES, GB, IT
ProviderLogin
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jp-morgan-chase-connectivity-api-openapi.yml Raw ↑

Other APIs JPMorgan Chase publishes across the network.

Notifications API
Accounts API
Recipients API
Webhooks API
Transactions API
Documents API
JPMorgan Chase Account Information API
JPMorgan Chase Account Restrictions API
JPMorgan Chase Account Services API
JPMorgan Chase Account Statements API
JPMorgan Chase Account Transactions API
JPMorgan Chase Account Updates API
Where this information came from

This is an independent, third-party profile of JPMorgan Chase Connectivity API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.