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 Payouts API

Pay By Bank - PayoutsPayments

JPMorgan Chase Payouts 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 Payouts. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 2 paths, and defines 11 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.

2 operations 2 paths 11 schemas 1 GET1 POST

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 2

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

Payouts 2

Pay By Bank - PayoutsPayments

POST
/payouts
Create Payouts
createPayout 1 param body → 202400401403409503
GET
/payouts/{id}
Retrieve Payouts
getPayoutId 1 param → 200400404503

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are Payout (6 properties), Error (5 properties), ErrorContext (4 properties), PayoutMetadata (4 properties). Each schema is shown below with its type and property counts.

PayoutDetails
Representation of a Payout and associated metadata.
PayoutAmount
object
The amount value and currency of a payout.Amount should be more than 0.01 with maximum of two decimal places allowed.
2 properties 2 required
ErrorContext
object
4 properties 1 required
ISOCurrencyCode
string
Currency of the money movement: a 3 alpha character ISO 4217 currency code.
StatusUpdatedAt
string
The last updated date and time of the status, in ISO 8601 format.
Payout
object
Representation of a Payout
6 properties 5 required
Value
string
The value representation of a monetary amount. The amount value should be more than 0.01 with maximum of two decimal places allowed.
Error
object
The error object returned by the API.
5 properties 1 required
PaymentType
string
The type of payment. List of supported payment types, their usage and categorization by region: Payment Type | Description -------------------------|----------…
UniqueResourceIdentifier
string
An immutable opaque string that uniquely identifies a resource.
PayoutMetadata
object
Representation of a Payout Metadata
4 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jp-morgan-chase-payouts-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 Payouts 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.