Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.
All 92 tools →
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/jp-morgan-chase-account-information-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: J.P. Morgan Business Direct Connect Account Information API
version: 6.5.1
description: Connect to retrieve account details, transactions, payment network information, and statements for eligible USD-denominated US checking, savings, and money market accounts using the Financial Data Exchange (FDX) standard with secure, paginated access and lightweight or detailed responses.
contact:
name: J.P. Morgan Corporate FDX Support
email: jpmorgan.business.direct.connect.support@jpmorgan.com
servers:
- url: https://api.payments.jpmorgan.com/fdx/v6
description: PRODUCTION - OAUTH
- url: https://api-mock.payments.jpmorgan.com/fdx/v6
description: MOCK
tags:
- name: Account Information
description: To retrieve the account details
paths:
/accounts:
get:
operationId: searchForAccounts
tags:
- Account Information
summary: Search for accounts
description: Return information for all of the customer's consented accounts or just those accounts identified in the `accountIds` request parameter. Use `ResultTypeQuery` parameter value of `lightweight` to retrieve minimal descriptive information and the `accountId` for each account. The `accountId` can then be used in the `getAccount` operation's path `/accounts/{accountId}` to retrieve full details about each account
parameters:
- $ref: '#/components/parameters/FapiInteractionIdHeader'
- $ref: '#/components/parameters/FdxApiActorTypeHeader'
- $ref: '#/components/parameters/FdxApiClientPublicKeyHeader'
- $ref: '#/components/parameters/FdxApiDataProviderIdHeader'
- $ref: '#/components/parameters/FdxApiDataRecipientIdHeader'
- $ref: '#/components/parameters/AccountId'
- $ref: '#/components/parameters/ResultTypeQuery'
- $ref: '#/components/parameters/OffsetQuery'
- $ref: '#/components/parameters/PageKeyQuery'
- $ref: '#/components/parameters/LimitQuery'
responses:
'200':
description: "Array of accounts (DepositAccount, LoanAccount, LineOfCreditAccount, InvestmentAccount,\n InsuranceAccount, AnnuityAccount, CommercialAccount, or DigitalWallet)"
headers:
x-fapi-interaction-id:
$ref: '#/components/parameters/FapiInteractionIdHeader'
content:
application/json:
schema:
$ref: '#/components/schemas/Accounts'
examples:
Search for accounts success response:
value:
page:
nextOffset: '2'
total: 3
links:
next:
href: /accounts?offSet=2&limit=10
accounts:
- accountCategory: COMMERCIAL_ACCOUNT
accountId: '10001'
accountType: CHECKING
nickname: Operating Account 1
status: OPEN
balanceAsOf: '2021-07-15T14:46:41.375Z'
currentAvailableBalance: 13300.35
'400':
description: 'Bad Request
**List of Error codes and Usage explanations.**
| Error Code | Usage |
| -------------- |-------------------------------------------------------------------------------------|
| 401 | Invalid Input, 11001:Input in Request for Client ID {0}. {1} |
| 10001 | Bad Request, 10001: Header parameter ''x-fapi-interaction-id'' is missing |'
headers:
x-fapi-interaction-id:
$ref: '#/components/parameters/FapiInteractionIdHeader'
content:
application/json:
schema:
anyOf:
- $ref: '#/components/schemas/Error'
- $ref: '#/components/schemas/PaymentError'
examples:
Invalid start or end date:
value:
code: '702'
message: Invalid start or end date
debugMessage: Provider custom developer-level error details for troubleshooting
Invalid date range:
value:
code: '703'
message: Invalid date range
debugMessage: Provider custom developer-level error details for troubleshooting
BadRequest:
value:
title: Bad Request
httpStatus: 400
traceId: 123e4567-e89b-12d3-a456-426614174000
requestId: client-req-001
context:
- code: '10001'
message: Header parameter 'x-fapi-interaction-id' is missing
location: HEADER
field: x-fapi-interaction-id
'401':
$ref: '#/components/responses/401'
'403':
$ref: '#/components/responses/403'
'404':
description: 'Not Found
**List of Error codes and Usage explanations.**
| Error Code | Usage |
| -------------- |---------------------------------------------------------------------------|
| 701 | Account not found, 12001:Account not found for Client ID {0}. {1} |'
headers:
x-fapi-interaction-id:
$ref: '#/components/parameters/FapiInteractionIdHeader'
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
examples:
Data not found for request parameters:
value:
code: '1107'
message: Data not found for request parameters
debugMessage: Provider custom developer-level error details for troubleshooting
'415':
$ref: '#/components/responses/415'
'422':
$ref: '#/components/responses/422'
'500':
$ref: '#/components/responses/500'
'501':
$ref: '#/components/responses/501'
'503':
$ref: '#/components/responses/503'
/accounts/{accountId}:
get:
operationId: getAccount
tags:
- Account Information
summary: Retrieve account details
description: Retrieve full details about the account identified by `{accountId}` parameter
parameters:
- $ref: '#/components/parameters/FapiInteractionIdHeader'
- $ref: '#/components/parameters/FdxApiActorTypeHeader'
- $ref: '#/components/parameters/FdxApiClientPublicKeyHeader'
- $ref: '#/components/parameters/FdxApiDataProviderIdHeader'
- $ref: '#/components/parameters/FdxApiDataRecipientIdHeader'
- $ref: '#/components/parameters/AccountIdPath'
responses:
'200':
description: This can be one of LoanAccount, DepositAccount, LineOfCreditAccount, InvestmentAccount, InsuranceAccount, AnnuityAccount, CommercialAccount, or DigitalWallet
headers:
x-fapi-interaction-id:
$ref: '#/components/parameters/FapiInteractionIdHeader'
content:
application/json:
schema:
$ref: '#/components/schemas/AccountWithDetails'
'400':
description: 'Bad Request
**List of Error codes and Usage explanations.**
| Error Code | Usage |
| -------------- |---------------------------------------------------------------------------|
| 401 | Invalid Input, 11001:Input in Request for Client ID {0}. {1} |
| 10001 | Bad Request, 10001: Header parameter ''x-fapi-interaction-id'' is missing |'
headers:
x-fapi-interaction-id:
$ref: '#/components/parameters/FapiInteractionIdHeader'
content:
application/json:
schema:
$ref: '#/components/schemas/PaymentError'
examples:
BadRequest:
value:
title: Bad Request
httpStatus: 400
traceId: 123e4567-e89b-12d3-a456-426614174000
requestId: client-req-001
context:
- code: '10001'
message: Header parameter 'x-fapi-interaction-id' is missing
location: HEADER
field: x-fapi-interaction-id
'401':
$ref: '#/components/responses/401'
'403':
$ref: '#/components/responses/403'
'404':
description: 'Not Found
**List of Error codes and Usage explanations.**
| Error Code | Usage |
| -------------- |---------------------------------------------------------------------------|
| 701 | Account not found, 12001:Account not found for Client ID {0}. {1} |'
headers:
x-fapi-interaction-id:
$ref: '#/components/parameters/FapiInteractionIdHeader'
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
examples:
Account not found:
value:
code: '701'
message: Account not found
debugMessage: Provider custom developer-level error details for troubleshooting
'415':
$ref: '#/components/responses/415'
'422':
$ref: '#/components/responses/422'
'500':
$ref: '#/components/responses/500'
'501':
$ref: '#/components/responses/501'
'503':
$ref: '#/components/responses/503'
components:
schemas:
PageMetadata:
title: Page Metadata
description: Offset IDs for paginated result sets
type: object
properties:
nextOffset:
type: string
example: '2'
description: Opaque identifier. Does not need to be numeric or have any specific pattern. Implementation specific Offset based pagination is not supported for /transactions.
prevOffset:
type: string
example: '1'
description: Opaque identifier. Does not need to be numeric or have any specific pattern. Implementation specific Offset based pagination is not supported for /transactions.
totalElements:
type: integer
example: 3
description: Total number of elements , can be used to validate against total number of elements returned in paginated response(s)
ErrorContext:
x-tags:
- common-error-model
- common-components
type: object
required:
- message
properties:
code:
type: string
description: JPMC Short code that identifies the error - publicly cataloged and documented
minLength: 5
maxLength: 5
pattern: ^[0-9]+$
message:
type: string
description: Human readable textual description of the error
minLength: 1
maxLength: 99
location:
type: string
title: The component of the request impacted, can either be 'body', 'query', 'header', or 'path'
description: The location of the error occurred in the request.
minLength: 1
maxLength: 99
enum:
- BODY
- PATH
- QUERY
- HEADER
field:
type: string
description: The field which caused the error. Where the location of the error occurred is BODY, the field would contain the JSON Path expression
minLength: 1
maxLength: 99
pattern: ^[\$0-9a-zA-Z-_.()\[\]{}'"\s@=><!?,]+$
additionalContext:
$ref: '#/components/schemas/AdditionalContext'
description: Error Context
Identifier:
title: Identifier
description: Value for a unique identifier
type: string
maxLength: 256
example: 5ff6a4b6fd9f4607c0a7ca0f037c62018693f940836d69b31d664f2257f4c623
Timestamp:
title: Timestamp
description: ISO 8601 date-time in format 'YYYY-MM-DDThh:mm:ss.nnn[Z|[+|-]hh:mm]' according to [IETF RFC3339](https://xml2rfc.tools.ietf.org/public/rfc/html/rfc3339.html#anchor14)
type: string
format: date-time
example: '2021-07-15T14:46:41.375Z'
AdditionalContext:
type: array
description: Additional details about the error based on a standard (e.g. ISO or Clearing codes)
items:
$ref: '#/components/schemas/StandardCodeContext'
minItems: 1
maxItems: 5
StandardCodeContext:
type: object
required:
- code
- message
- type
properties:
type:
title: CategoryType
type: string
description: "Category of the error code such as Business 21000 Invalid Access Token \n|Category Type | Description\n|--------------|-----------------\n|Business 21000 | Invalid Request, Client ID {ClientIdName} not valid\n|Server 22002 | Error connecting to Account Product Service for Client Id {ClientIdName}, account Id {accountHashId} for retrieving account details"
minLength: 2
maxLength: 16
code:
type: string
description: Short code that identifies the error - publicly cataloged and documented
minLength: 2
maxLength: 10
pattern: ^[a-zA-Z0-9]+$
message:
type: string
description: Human readable textual description of the error
minLength: 1
maxLength: 99
ResultType:
title: Result Type
description: Flag to indicate if you want a lightweight array of metadata (AccountDescriptor or Tax or Operations) or full item details (Account or a Tax subclass or Availability details). If set to 'lightweight', should only return the fields associated with the metadata entity.
type: string
enum:
- details
- lightweight
default: lightweight
HateoasLink:
title: HATEOAS Link
description: REST application constraint (Hypermedia As The Engine Of Application State)
required:
- href
type: object
properties:
href:
type: string
format: uri-reference
description: URL to invoke the action on the resource
example: https://api.fi.com/fdx/v4/accounts/12345
action:
description: HTTP Method to use for the request
$ref: '#/components/schemas/HttpAction'
rel:
description: Relation of this link to its containing entity, as defined by and with many example relation values at [IETF RFC5988](https://datatracker.ietf.org/doc/html/rfc5988)
type: string
types:
type: array
minItems: 0
items:
$ref: '#/components/schemas/ContentTypes'
ActorType:
title: FDX API Actor Type
description: 'This parameter is optional. The API only supports BATCH operations. default: BATCH'
type: string
default: BATCH
enum:
- BATCH
- USER
CommercialAccount:
title: Commercial Account entity
description: Information for a commercial account type
type: object
allOf:
- $ref: '#/components/schemas/Account'
- type: object
properties:
balanceAsOf:
description: Year, month and the day for which the balance is being reported.
$ref: '#/components/schemas/Timestamp'
type: string
format: date-time
example: '2021-07-15T14:46:41.375Z'
openingLedgerBalance:
type: number
description: Opening ledger balance for the date specified in balanceAsOf.
example: 81572.35
closingLedgerBalance:
type: number
description: Closing ledger balance for the date specified in balanceAsOf.
example: 80572.35
currentLedgerBalance:
type: number
description: Current ledger balance
example: 80572.35
currentAvailableBalance:
type: number
description: Current available balance as displayed to the user within Online Banking.
example: 80572.35
Accounts:
title: Accounts entity
description: An optionally paginated array of accounts
type: object
allOf:
- $ref: '#/components/schemas/PaginatedArray'
- type: object
properties:
accounts:
type: array
minItems: 0
description: An array of accounts with entity types dependent on the account type commercial
items:
$ref: '#/components/schemas/AccountWithDetails'
DataCluster:
title: Data Cluster
description: Name of permissioned Data Cluster. For Data Cluster definitions refer to the Consent Components > Data Clusters section of the User Experience Guidelines document included in the FDX API. `ACCOUNT_PAYMENTS` is deprecated and replaced with `PAYMENT_SUPPORT` in FDX release V6.1.0, `ACCOUNT_PAYMENTS` will be removed with V7 release
type: string
enum:
- ACCOUNT_BASIC
- ACCOUNT_DETAILED
- ACCOUNT_PAYMENTS
- BALANCES
- BILLS
- CUSTOMER_CONTACT
- CUSTOMER_PERSONAL
- IMAGES
- INVESTMENTS
- NOTIFICATIONS
- PAYMENT_SUPPORT
- REWARDS
- SCHEDULED_PAYMENTS
- SOCIAL_SECURITY_NUMBER
- STATEMENTS
- TAX
- TERMS_AND_CONDITIONS
- TRANSACTIONS
- TRANSFERS
Error:
title: Error
description: An error entity which can be used at the API level for error responses or at the account level to indicate a problem specific to a particular account
type: object
properties:
code:
type: string
description: Long term persistent identifier which can be used to trace error condition back to log information
example: '601'
message:
type: string
description: End user displayable information which might help the customer diagnose an error
example: Customer not found
debugMessage:
type: string
description: Message used to debug the root cause of the error. Contents should not be used in consumer's business logic. Can change at any time and should only be used for consumer to communicate with the data provider about an issue. Provider can include an error GUID in message for their use.
example: 11005:Invalid Customer - Customer Not Found for Client ID A_JPMC_CB_777_SIT_114355
AccountDescriptor:
title: Account Descriptor entity
description: This descriptor provides minimal information about the account for use in lightweight arrays
type: object
required:
- accountCategory
discriminator:
propertyName: accountCategory
properties:
accountCategory:
$ref: '#/components/schemas/AccountCategory'
description: The entity type of this Account
accountId:
description: Unique account identifier that is different from the account number.
example: '123456789'
$ref: '#/components/schemas/Identifier'
type: string
error:
description: Present if an error was encountered while retrieving this account
$ref: '#/components/schemas/Error'
accountType:
$ref: '#/components/schemas/AccountType'
description: Account type
example: CHECKING
accountNumberDisplay:
description: Masked account number to be used to display to aid end-user identification of the account.
type: string
example: '9876'
productName:
description: Marketed product name for this account. Used in UIs to assist in account selection.
type: string
nickname:
description: Name given by the user. Used in UIs to assist in account selection
type: string
example: STONEMEN EXPERT MASONS LLC
status:
description: 'Account status. Suggested values are: OPEN, CLOSED, PENDINGOPEN, PENDINGCLOSE, PAID, DELINQUENT, NEGATIVECURRENTBALANCE, RESTRICTED'
$ref: '#/components/schemas/AccountStatus'
example: OPEN
currency:
$ref: '#/components/schemas/Currency'
description: Account currency
example: USD
accountOpenDate:
$ref: '#/components/schemas/DateString'
description: Account opening date
dataClusters:
type: array
minItems: 0
description: An array of supported data cluster scopes for this account. I.e. ACCOUNT_DETAILED, TRANSACTIONS, STATEMENTS, REWARDS, etc.
items:
$ref: '#/components/schemas/DataCluster'
domicile:
$ref: '#/components/schemas/Domicile'
description: The country and region of the account's legal jurisdiction
example: US
PaymentError:
type: object
x-tags:
- common-error-model
- common-components
title: Error
description: Common Error Model
properties:
title:
type: string
title: Short humanly-readable title of the error.
minLength: 1
maxLength: 100
httpStatus:
type: integer
default: 400
title: HTTP Status Code
traceId:
type: string
title: JPMC Assigned traced identifier
requestId:
type: string
title: The 'client originated' requestId
context:
type: array
title: Provides additional context and detail on the validation errors
items:
$ref: '#/components/schemas/ErrorContext'
minItems: 1
maxItems: 100
required:
- title
readOnly: true
String64:
title: String 64
description: String of maximum length 64
type: string
maxLength: 64
AccountStatus:
title: Account Status
description: The status of an account
type: string
enum:
- OPEN
- CLOSED
- DELINQUENT
- NEGATIVECURRENTBALANCE
- PAID
- PENDINGCLOSE
- PENDINGOPEN
- RESTRICTED
Currency:
title: Currency entity
description: Represents an international currency
type: object
properties:
currencyRate:
type: number
description: Currency rate between original and converted currency
currencyCode:
$ref: '#/components/schemas/Iso4217CurrencyCode'
description: ISO 4217 currency code
originalCurrencyCode:
$ref: '#/components/schemas/Iso4217CurrencyCode'
description: Original ISO 4217 currency code
Account:
title: Account entity
description: An abstract account entity that concrete account entities extend
type: object
allOf:
- $ref: '#/components/schemas/AccountDescriptor'
- type: object
properties:
lineOfBusiness:
description: The line of business, such as consumer, consumer joint, small business, corporate, etc.
type: string
example: CORPORATE
balanceType:
$ref: '#/components/schemas/BalanceType'
description: ASSET (positive transaction amount increases balance), LIABILITY (positive transaction amount decreases balance)
example: ASSET
transactionsIncluded:
type: boolean
description: The API requires a separate call to transactions endpoint to retrieve transactions.
example: false
domicile:
$ref: '#/components/schemas/Domicile'
description: The country and region of the account's legal jurisdiction
example: US
Iso4217CurrencyCode:
title: ISO 4217 Currency Code
description: Currency, fund and precious metal codes as of Jan. 1, 2023 per [ISO 4217 Currency Code Maintenance](https://www.six-group.com/en/products-services/financial-information/data-standards.html)
type: string
enum:
- USD
BalanceType:
title: Balance Type
description: "Type of balance for the account.\n * `ASSET`: Positive transaction amount increases balance\n * `LIABILITY`: Positive transaction amount decreases balance"
type: string
enum:
- ASSET
- LIABILITY
PageMetadataLinks:
title: Page Metadata Links
description: Resource URLs for retrieving next or previous datasets
type: object
properties:
next:
$ref: '#/components/schemas/HateoasLink'
description: Resource URL for retrieving next dataset
prev:
$ref: '#/components/schemas/HateoasLink'
description: Resource URL for retrieving previous dataset. It is not supported for /transactions, which only supports forward traversal.
Domicile:
title: Domicile entity
description: Country and region of country for the legal jurisdiction of an entity
type: object
properties:
region:
$ref: '#/components/schemas/String64'
description: Country sub-division; state or province or territory
country:
$ref: '#/components/schemas/Iso3166CountryCode'
description: ISO 3166 Country Code
Iso3166CountryCode:
title: ISO 3166 Country Code
description: ISO 3166-1 alpha-2 codes as of April 5, 2023, from officially assigned Country Codes on [ISO Online Browsing Platform](https://www.iso.org/obp/ui/). Change log is at [ISO 3166 Maintenance Agency](https://www.iso.org/fr/committee/48750.html?t=3V3rukDb61p05Wd6ojyTRvE0S3Yg_fZgUjrLjHWcd9-mDmTKHOGjbX3nEJ3SqHar&view=documents#section-isodocuments-top)
type: string
enum:
- AD
- AE
- AF
- AG
- AI
- AL
- AM
- AO
- AQ
- AR
- AS
- AT
- AU
- AW
- AX
- AZ
- BA
- BB
- BD
- BE
- BF
- BG
- BH
- BI
- BJ
- BL
- BM
- BN
- BO
- BQ
- BR
- BS
- BT
- BV
- BW
- BY
- BZ
- CA
- CC
- CD
- CF
- CG
- CH
- CI
- CK
- CL
- CM
- CN
- CO
- CR
- CU
- CV
- CW
- CX
- CY
- CZ
- DE
- DJ
- DK
- DM
- DO
- DZ
- EC
- EE
- EG
- EH
- ER
- ES
- ET
- FI
- FJ
- FK
- FM
- FO
- FR
- GA
- GB
- GD
- GE
- GF
- GG
- GH
- GI
- GL
- GM
- GN
- GP
- GQ
- GR
- GS
- GT
- GU
- GW
- GY
- HK
- HM
- HN
- HR
- HT
- HU
- ID
- IE
- IL
- IM
- IN
- IO
- IQ
- IR
- IS
- IT
- JE
- JM
- JO
- JP
- KE
- KG
- KH
- KI
- KM
- KN
- KP
- KR
- KW
- KY
- KZ
- LA
- LB
- LC
- LI
- LK
- LR
- LS
- LT
- LU
- LV
- LY
- MA
- MC
- MD
- ME
- MF
- MG
- MH
- MK
- ML
- MM
- MN
- MO
- MP
- MQ
- MR
- MS
- MT
- MU
- MV
- MW
- MX
- MY
- MZ
- NA
- NC
- NE
- NF
- NG
- NI
- NL
- NP
- NR
- NU
- NZ
- OM
- PA
- PE
- PF
- PG
- PH
- PK
- PL
- PM
- PN
- PR
- PS
- PT
- PW
- PY
- QA
- RE
- RO
- RS
- RU
- RW
- SA
- SB
- SC
- SD
- SE
- SG
- SH
- SI
- SJ
- SK
- SL
- SM
- SN
- SO
- SR
- SS
- ST
- SV
- SX
- SY
- SZ
- TC
- TD
- TF
- TG
- TH
- TJ
- TK
- TL
- TM
- TN
- TO
- TR
- TT
- TV
- TW
- TZ
- UA
- UG
- UM
- US
- UY
- UZ
- VA
- VC
- VE
- VG
- VI
- VN
- VU
- WF
- WS
- YE
- YT
- ZA
- ZM
- ZW
HttpAction:
title: HTTP Action Type
description: HTTP Methods to use for requests
type: string
enum:
- DELETE
- GET
- PATCH
- POST
- PUT
DateString:
title: Date String
description: ISO 8601 full-date in format 'YYYY-MM-DD' according to [IETF RFC3339](https://xml2rfc.tools.ietf.org/public/rfc/html/rfc3339.html#anchor14)
type: string
format: date
maxLength: 10
example: '2021-07-15'
ContentTypes:
title: Content Types
description: Types of document formats. (Suggested values)
type: string
enum:
- application/json
- application/pdf
- application/zip
- image/gif
- image/jpeg
- image/png
- image/tiff
PaginatedArray:
title: Paginated Array
description: Base class for results that may be paginated
type: object
properties:
page:
$ref: '#/components/schemas/PageMetadata'
description: Offset IDs for navigating result sets
links:
$ref: '#/components/schemas/PageMetadataLinks'
description: Resource URLs for navigating result sets
AccountWithDetails:
title: Account With Details entity
description: An instance of an account with full details
type: object
discriminator:
propertyName: accountCategory
mapping:
COMMERCIAL_ACCOUNT: '#/components/schemas/CommercialAccount'
oneOf:
- $ref: '#/components/schemas/CommercialAccount'
AccountType:
title: Account Type
description: "The type of an account.\n | Value | Description |\n |-----|-----|\n | CHECKING | A deposit account held at a financial institution that allows withdrawals and deposits |\n | COMMERCIALDEPOSIT | Deposit Account for Commercial Customers e.g. Business Trust Account |"
type: string
enum:
- CHECKING
- COMMERCIALDEPOSIT
- MONEYMARKET
AccountCategory:
title: Account Category type
description: The category of account
type: string
enum:
- COMMERCIAL_ACCOUNT
parameters:
FapiInteractionIdHeader:
name: x-fapi-interaction-id
in: header
description: Unique identifier for this interaction as an IETF RFC 4122 UUID. Used across all FDX API requests and responses. This parameter is required.
schema:
type: string
required: true
examples:
Scenario-1:
summary: Sample FAPI Interaction Id
value: c770aef3-6784-41f7-8e0e-ff5f97bddb3a
ResultTypeQuery:
name: resultType
in: query
description: Flag to indicate if you want a lightweight array of metadata (AccountDescriptor or Tax or Operations) or full item details (Account or a Tax subclass or Availability details). If set to 'lightweight', should only return the fields associated with the metadata entity. This field is not required, defaults to lightweight
required: false
schema:
$ref: '#/components/schemas/ResultType'
FdxApiDataProviderIdHeader:
name: FDX-API-Data-Provider-Id
in: header
description: ID for the financial institution responding to the request
schema:
$ref: '#/components/schemas/Identifier'
description: If the FDX API service is provided by a service bureau which uses the same end point for multiple institutions, the FDX API client MUST provide a header that identifies the desired financial institutio
# --- truncated at 32 KB (43 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/jp-morgan-chase/refs/heads/main/openapi/jp-morgan-chase-account-information-api-openapi.yml