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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
JPMorgan Chase

Recipients API

Streamline how you set up, manage, and verify payees by creating, updating, listing, and validating recipients for your payment transactions. This helps keep your payment workflows organized and secure without manual tracking.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

This API exposes 5 operations across 3 paths, and defines 37 schemas. It is described by OpenAPI 3.0.1, at version 1.0.55.

Requests are made against 3 base URLs: https://api.payments.jpmorgan.com/embedded/v1, https://api-mock.payments.jpmorgan.com/embedded/v1, https://api-sandbox.payments.jpmorgan.com/embedded/v1.

5 operations 3 paths 37 schemas 2 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0.55
Base URL
https://api.payments.jpmorgan.com/embedded/v1
Contact
JPMC Technical Services Support
Resource Areas
1

Paths & Operations 5

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

Recipients 5

Set up and manage who can be paid through transactions.

GET
/recipients
List recipients
getAllRecipients 6 params → 200400401403404500503
POST
/recipients
Create recipient
createRecipient 1 param body → 201400401403404500503
GET
/recipients/{id}
Get recipient
getRecipient 2 params → 200400401403404500503
POST
/recipients/{id}
Update recipient
amendRecipient 2 params body → 200400401403404500503
POST
/recipients/{id}/verify-microdeposit
Creates a microdeposits verification process.
recipientsVerification 2 params body → 200400401403404500503

Schemas 37

The contract defines 37 schemas that model the data the API accepts and returns. The most detailed are Recipient (12 properties), RecipientAddress (9 properties), RecipientPartyDetails (8 properties), Codes (6 properties). Each schema is shown below with its type and property counts.

RecipientType
string
RecipientStatus
string
Callback event type needs to send to notsub for correct status.
PageMetaData
object
3 properties
CountryCode
string
Two letter country code based on ISO 3166 standard
RecipientAddress
object
Address details for the recipient. Mandatory for payments using the RTP payment type.
9 properties 3 required
PartyType
string
RecipientContact
object
3 properties 2 required
RecipientIdentity
object
2 properties 2 required
RecipientPartyDetails
object
8 properties 1 required
AccountNumber
string
Demand Deposit Account number or International Account Number (IBAN).
AccountType
string
Type of bank account.
RoutingNumber
string
Routing number corresponding to the routing code type
RoutingInformationTransactionType
string
Type of transaction.
RoutingCodeType
string
Type of routing code.
RoutingInformation
object
3 properties 3 required
CurrencyCode
string
Three letter currency code based on ISO 4217 standard
RecipientAccount
object
Bank account details of the recipient.
5 properties 2 required
ApiErrorReasonV2
object
Schema representing detailed reasons for an API error, including code, location, and message.
4 properties 1 required
ApiError
object
5 properties 3 required
Result
object
3 properties
Codes
object
6 properties
ClearingSystemId
object
2 properties
FinancialInstitutionId
object
1 property
ProviderResponse
object
Contains additional, unstructured information from the provider.
Details
object
4 properties
Responses
object
3 properties
AccountValidationResponse
object
3 properties
CardHolderName
string
Name on the credit/debit card
ExpiryDate
string
Expiry date of card in the format MM-YY
RecipientCard
object
3 properties 3 required
Recipient
object
12 properties 2 required
ListRecipientsResponse
object
RecipientRequest
object
6 properties
RecipientCardUpdate
object
2 properties
UpdateRecipientRequest
object
4 properties
MicrodepositAmounts
object
Microdeposit amount verification
1 property 1 required
MicrodepositVerificationResponse
object
Microdeposit verification outcome
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs JPMorgan Chase publishes across the network.

Digital Onboarding API
AE Profile APIs.io
Consumer Profile Management API
AE Profile APIs.io
Tokenization API
AE Profile APIs.io
Reporting API
AE Profile APIs.io
Notifications API
AE Profile APIs.io
Request to Pay via QR Code API
AE Profile APIs.io
Checkout API
AE Profile APIs.io
Dispute Management API
AE Profile APIs.io
Accounts API
AE Profile APIs.io
Alerts and Decisioning API
AE Profile APIs.io
Product Configuration API
AE Profile APIs.io
Webhooks API
AE Profile APIs.io
#Recipients
← Back to R APIs
API Details
ID
jp-morgan-chase:recipients-api
Base URL
https://api.payments.jpmorgan.com/embedded/v1
Docs
https://developer.payments.jpmorgan.com/api
Provider
JPMorgan Chase
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=recipients-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/recipients-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of Recipients 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.