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

JPMorgan Chase Document requests API

View details of requests for documents.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

This API exposes 3 operations across 3 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version 1.0.18.

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

3 operations 3 paths 13 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.18
Base URL
https://api.payments.jpmorgan.com/onboarding/v1
Authentication
HTTP Bearer
Contact
JPMC Technical Services Support
Resource Areas
1

Authentication & Security 1

JPMorgan Chase Document requests API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). By default, every request must be authenticated.

Paths & Operations 3

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

Document requests 3

View details of requests for documents.

GET
/document-requests
List document requests
smbdo-listDocumentRequests 3 params → 200400401403404500503
GET
/document-requests/{id}
Get document request
smbdo-getDocumentRequest 2 params → 200400401403404500503
POST
/document-requests/{id}/submit
Submit a document request
smbdo-submitDocumentRequest 3 params → 202400401403404409422500

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are DocumentRequestResponse (12 properties), schemas-ApiError (5 properties), ApiErrorContext (4 properties), DocumentRequestRequirement (3 properties). Each schema is shown below with its type and property counts.

DocumentTypeSmbdo
string
Supported document types
DocumentRequestRequirement
object
3 properties 1 required
ApiErrorContext
object
Context of the API error.
4 properties 1 required
DocumentRequestId
string
Unique Document Request identifier.
DocumentRequestResponse
object
12 properties
schemas-ApiError
object
An API error.
5 properties 2 required
ClientId
string
A client's unique ID
PageMetaData
object
Page metadata.
3 properties
DocumentRequestListResponse
object
2 properties 2 required
ValidForDays
integer
Number of days from the day of its creation that this request will expire.
DocumentRequestOutstanding
object
Outstanding items on the document request.
1 property 1 required
PartyId
string
Organization/Individual party id, that uniquely identifies the party.
DocumentRequestStatus
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jp-morgan-chase-document-requests-api-openapi.yml Raw ↑

Other APIs JPMorgan Chase publishes across the network.

Notifications API
AE Profile APIs.io
Accounts API
AE Profile APIs.io
Recipients API
AE Profile APIs.io
Webhooks API
AE Profile APIs.io
Transactions API
AE Profile APIs.io
Documents API
AE Profile APIs.io
JPMorgan Chase Account Information API
AE Profile APIs.io
JPMorgan Chase Account Restrictions API
AE Profile APIs.io
JPMorgan Chase Account Services API
AE Profile APIs.io
JPMorgan Chase Account Statements API
AE Profile APIs.io
JPMorgan Chase Account Transactions API
AE Profile APIs.io
JPMorgan Chase Account Updates API
AE Profile APIs.io
#Document requests
← Back to J APIs
API Details
ID
jp-morgan-chase:jp-morgan-chase-document-requests-api
Base URL
https://api.payments.jpmorgan.com/onboarding/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=jp-morgan-chase-document-requests-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/jp-morgan-chase-document-requests-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 JPMorgan Chase Document requests 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.