JPMorgan Chase

JPMorgan Chase AIS API

The AIS API from JPMorgan Chase — 6 operation(s) for ais.

GitHub OpenAPI

Operations 6

POST /aisp/providers Request for Providers #
POST /aisp/consent/provider Request to Access Account Information Services #
POST /aisp/authorize Send Authorized Token Issued by Provider #
POST /aisp/accounts Request for Account Information #
POST /aisp/transactions Request for Transaction Details #
POST /aisp/holderinfo Request for Account Holder Information #

Documentation

📖
Documentation
https://developer.payments.jpmorgan.com/api
📖
APIReference
https://developer.payments.jpmorgan.com/api/llm-content?path=en%2Fapi%2Fembedded-finance-solutions%2Fembedded-payments%2Fonboarding-oas.md
📖
APIReference
https://developer.payments.jpmorgan.com/api/llm-content?path=en%2Fapi%2Fcommerce%2Foptimization-protection%2Fconsumer-profile%2Fconsumer-profile-oas.md
📖
APIReference
https://developer.payments.jpmorgan.com/api/llm-content?path=en%2Fapi%2Fcommerce%2Foptimization-protection%2Ftokenization%2Ftokenization-oas.md
📖
APIReference
https://developer.payments.jpmorgan.com/api/llm-content?path=en%2Fapi%2Fcommerce%2Foptimization-protection%2Freporting%2Freporting-oas.md
📖
APIReference
https://developer.payments.jpmorgan.com/api/llm-content?path=en%2Fapi%2Ftreasury%2Freceivables%2Frequest-to-pay-api.md
📖
APIReference
https://developer.payments.jpmorgan.com/api/llm-content?path=en%2Fapi%2Fcommerce%2Fonline-payments%2Fcheckout%2Fcheckout-oas.md
📖
APIReference
https://developer.payments.jpmorgan.com/api/llm-content?path=en%2Fapi%2Fcommerce%2Fdispute-management%2Fdispute-management-oas.md
📖
APIReference
https://developer.payments.jpmorgan.com/api/llm-content?path=en%2Fapi%2Ffraud-solutions%2Falerts-and-decisioning%2Foas.md
📖
APIReference
https://developer.payments.jpmorgan.com/api/llm-content?path=en%2Fapi%2Fcommerce%2Fproduct-configuration%2Fproduct-configuration-oas.md
📖
APIReference
https://developer.payments.jpmorgan.com/api/llm-content?path=en%2Fapi%2Fcommerce%2Foptimization-protection%2F3-d-secure%2F3-d-secure-1.md
📖
APIReference
https://developer.payments.jpmorgan.com/api/llm-content?path=en%2Fapi%2Fcommerce%2Foptimization-protection%2Faccount-updater%2Faccount-updater-oas.md
📖
APIReference
https://developer.payments.jpmorgan.com/api/llm-content?path=en%2Fapi%2Ftreasury%2Fglobal-payments%2Fglobal-payments%2Fglobal-payments-oas.md
📖
APIReference
https://developer.payments.jpmorgan.com/api/llm-content?path=en%2Fapi%2Fliquidity-account-solutions%2Fbda-balances%2Faccounts-oas.md
📖
APIReference
https://developer.payments.jpmorgan.com/api/llm-content?path=en%2Fapi%2Ffraud-solutions%2Fvalidation-services%2Fvalidation-services-oas.md
📖
APIReference
https://developer.payments.jpmorgan.com/api/llm-content?path=en%2Fapi%2Fcommerce%2Foptimization-protection%2Fwallet-decryption%2Fwallet-decryption-oas.md

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/jp-morgan-chase/refs/heads/main/openapi/jp-morgan-chase-ais-api-openapi.yml

Work with this as data

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-ais-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.

GitHub Google LinkedIn

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

OpenAPI Specification

jp-morgan-chase-ais-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Pay By Bank PIS AIS API
  version: 1.1.4
  description: "## Pay By Bank v1 - PIS API\n\n---\n\n> J.P. Morgan as a registered Third Party Provider (**TPP**) of Open Banking services,\n> offers a seamless integration platform for Pay by Bank such that:\n> - clients can initiate payments (serving as a Payment Initiation Service Provider, or **PISP**) \n>"
  contact:
    name: JPMorgan Chase & Co. API Support
    email: imsd.security.operations@jpmorgan.com
    url: https://developer.payments.jpmorgan.com/contact/support
servers:
- url: https://apigateway.jpmorgan.com/tsapi/v1
  description: PRODUCTION - MTLS
- url: https://api-mock.payments.jpmorgan.com/tsapi/v1
  description: MOCK
tags:
- name: AIS
paths:
  /aisp/providers:
    post:
      deprecated: true
      summary: Request for Providers
      description: '<!-- theme: warning-->

        > Deprecated

        >

        > Sunset: 30 May 2026

        - This request retrieves a list of ASPSPs reachable using J.P. Morgan''s AISP services in each country.

        - For the purposes of this API, ASPSPs are referred to as Providers.

        - The request for retrieving a particular country''s list of supported Providers must contain the correct country code'
      tags:
      - AIS
      operationId: retrieveAISProviders
      parameters:
      - $ref: '#/components/parameters/ContentType'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ProvidersRequest'
        required: false
      x-examples:
      - name: ExampleProvidersRequest
        description: Example request to retrieve providers
        parameters:
          body:
            countryCode: XF
      responses:
        '200':
          description: Successful
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ProvidersResponse'
              examples:
                ExamplesProvidersResponse:
                  $ref: '#/components/examples/ProvidersResponseExample'
        '400':
          description: 'Bad Request.


            **The following table lists and describes the error codes applicable**

            | Error Code | Meaning                                                                                              |

            |------------|------------------------------------------------------------------------------------------------------|

            | AISP-001   |Values are missing for properties: `<properties>`                                                     |

            | AISP-002   |Invalid consent scopes: `<invalid_scopes>`                                                            |

            | AISP-003   |Invalid JSON format                                                                                   |

            | AISP-006   |Report not found with requested payload                                                               |

            | AISP-007   |Customer did not consent to the Provider:<invalid_payload>                                            |

            | AISP-008   |Provider not found for country code: `<invalid_country_code>` or provider code:`<invalid_provider_code>` This error code will appear if an incorrect providerCode is given|

            | AISP-010   |ClientID not present in the header                                                                    |

            | AISP-012   |Required properties are missing: `<missing_fields>`                                                   |

            | AISP-013   |Invalid properties exist: `<additional_fields>`                                                       |

            | AISP-014   |Providers are not available with countryCode: `<country_code>`                                        |

            | AISP-015   |Consent expired, please call consent provider API to re-consent                                       |

            | AISP-016   |Bad request                                                                                           |

            | AISP-017   |The consent has already been revoked                                                                  |

            | AISP-017   |Refresh is not possible because the consent has expired                                               |

            | AISP-017   |A consent with such an id does not exist                                                              |

            | AISP-017   |Refresh is not possible because the consent has been revoked                                          |

            | AISP-017   |The value of consent scopes parameter is invalid                                                      |

            | AISP-017   |The value of consent scopes parameter is not allowed for the client or/and by the provider            |

            | AISP-017   |The next refresh attempt will be allowed according to next_refresh_possible attribute or connection''s status is inactive|

            | AISP-017   |The client tried to connect, reconnect or fetch a connection, but it appears to be disabled           |

            | AISP-017   |Bad requestWe could not find a connection with the requested connection_id                            |

            | AISP-017   |We have received an invalid Date format                                                               |

            | AISP-017   |The passed from_date - to_date interval is out of consent from_date - to_date range                   |

            | AISP-017   |Sending a date value that does not fit in admissible range                                            |

            | AISP-017   |We have received an invalid DateTime format                                                           |

            | AISP-017   |Sending a datetime value that does not fit in admissible range                                        |

            | AISP-017   |The value of fetch_scopes parameter is invalid                                                        |

            | AISP-017   |Fetching holder_info for this provider is not supported                                               |

            | AISP-017   |Invalid consent from_date value, either out of range or a wrong date format                           |

            | AISP-017   |Invalid consent period_days value or not allowed by provider                                          |

            | AISP-017   |Invalid from_date value, either out of range or wrong date format                                     |

            | AISP-017   |Invalid to_date value, either out of range or wrong date format                                       |

            | AISP-017   |We have received some other request format instead of JSON, or the body could not be parsed           |

            | AISP-017   |The accessed provider has the disabled status. Hence, is no longer supported                          |

            | AISP-017   |The requested provider has the inactive status. That means that new connections cannot be created while the current ones cannot be refreshed or reconnected|

            | AISP-017   |Sending a provider_code that is not present in our system                                             |

            | AISP-017   |The connection''s provider has no interactive step                                                     |

            | AISP-017   |Too many connections are being processed at the same time from one application                        |

            | AISP-018   |Customer did not consent to provider `<provider_code>`, please call consent provider API to re-consent|

            | AISP-019   |Provider `<provider_code>` does not support the requested service                                     |'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              examples:
                InvalidJSONFormatExample:
                  $ref: '#/components/examples/InvalidJSONFormatExample'
        '500':
          description: 'Internal server error


            **The following table lists and describes the error codes applicable**

            | Error Code | Meaning              |

            |------------|----------------------|

            | AISP-020   |Internal server error |'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '503':
          description: "Service Unavailable\n\n**The following table lists and describes the error codes applicable**\n| Error Code | Meaning                                       |\n|------------|-----------------------------------------------|\n| AISP-004   |System exception                               |    \n| AISP-005   |Consent terms not found with requested payload |"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
  /aisp/consent/provider:
    post:
      deprecated: true
      summary: Request to Access Account Information Services
      description: '<!-- theme: warning-->

        > Deprecated

        >

        > Sunset: 30 May 2026

        - This request allows the PSU to consent to J.P. Morgan accessing their

        account information at a particular `Provider`.'
      tags:
      - AIS
      operationId: createAccountConsents
      parameters:
      - $ref: '#/components/parameters/ContentType'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ConsentRequest'
            examples:
              ExampleConsentRequest:
                $ref: '#/components/examples/ConsentRequestExample'
        required: true
      x-examples:
      - name: ExampleConsentRequest
        description: Example Consent Request
        parameters:
          body:
            customerId: CUST_QA02103453A
            countryCode: XF
            providerCode: fake_oauth_client_xf
            consentScopes:
            - account_details
            - transactions_details
            - holder_information
            consentDuration: 90
            returnToUrl: https://sites.jpmchase.com/sites/cib
      responses:
        '200':
          description: Successful
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ConsentResponse'
              examples:
                ExampleConsentResponse:
                  $ref: '#/components/examples/ConsentResponseExample'
        '400':
          description: 'Bad Request.


            **The following table lists and describes the error codes applicable**

            | Error Code | Meaning                                                                                              |

            |------------|------------------------------------------------------------------------------------------------------|

            | AISP-001   |Values are missing for properties: `<properties>`                                                     |

            | AISP-002   |Invalid consent scopes: `<invalid_scopes>`                                                            |

            | AISP-003   |Invalid JSON format                                                                                   |

            | AISP-006   |Report not found with requested payload                                                               |

            | AISP-007   |Customer did not consent to the Provider:<invalid_payload>                                            |

            | AISP-008   |Provider not found for country code: `<invalid_country_code>` or provider code:`<invalid_provider_code>` This error code will appear if an incorrect providerCode is given|

            | AISP-010   |ClientID not present in the header                                                                    |

            | AISP-012   |Required properties are missing: `<missing_fields>`                                                   |

            | AISP-013   |Invalid properties exist: `<additional_fields>`                                                       |

            | AISP-014   |Providers are not available with countryCode: `<country_code>`                                        |

            | AISP-015   |Consent expired, please call consent provider API to re-consent                                       |

            | AISP-016   |Bad request                                                                                           |

            | AISP-017   |The consent has already been revoked                                                                  |

            | AISP-017   |Refresh is not possible because the consent has expired                                               |

            | AISP-017   |A consent with such an id does not exist                                                              |

            | AISP-017   |Refresh is not possible because the consent has been revoked                                          |

            | AISP-017   |The value of consent scopes parameter is invalid                                                      |

            | AISP-017   |The value of consent scopes parameter is not allowed for the client or/and by the provider            |

            | AISP-017   |The next refresh attempt will be allowed according to next_refresh_possible attribute or connection''s status is inactive|

            | AISP-017   |The client tried to connect, reconnect or fetch a connection, but it appears to be disabled           |

            | AISP-017   |Bad requestWe could not find a connection with the requested connection_id                            |

            | AISP-017   |We have received an invalid Date format                                                               |

            | AISP-017   |The passed from_date - to_date interval is out of consent from_date - to_date range                   |

            | AISP-017   |Sending a date value that does not fit in admissible range                                            |

            | AISP-017   |We have received an invalid DateTime format                                                           |

            | AISP-017   |Sending a datetime value that does not fit in admissible range                                        |

            | AISP-017   |The value of fetch_scopes parameter is invalid                                                        |

            | AISP-017   |Fetching holder_info for this provider is not supported                                               |

            | AISP-017   |Invalid consent from_date value, either out of range or a wrong date format                           |

            | AISP-017   |Invalid consent period_days value or not allowed by provider                                          |

            | AISP-017   |Invalid from_date value, either out of range or wrong date format                                     |

            | AISP-017   |Invalid to_date value, either out of range or wrong date format                                       |

            | AISP-017   |We have received some other request format instead of JSON, or the body could not be parsed           |

            | AISP-017   |The accessed provider has the disabled status. Hence, is no longer supported                          |

            | AISP-017   |The requested provider has the inactive status. That means that new connections cannot be created while the current ones cannot be refreshed or reconnected|

            | AISP-017   |Sending a provider_code that is not present in our system                                             |

            | AISP-017   |The connection''s provider has no interactive step                                                     |

            | AISP-017   |Too many connections are being processed at the same time from one application                        |

            | AISP-018   |Customer did not consent to provider `<provider_code>`, please call consent provider API to re-consent|

            | AISP-019   |Provider `<provider_code>` does not support the requested service                                     |'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              examples:
                InvalidJSONFormatExample:
                  $ref: '#/components/examples/InvalidJSONFormatExample'
        '500':
          description: 'Internal server error


            **The following table lists and describes the error codes applicable**

            | Error Code | Meaning              |

            |------------|----------------------|

            | AISP-020   |Internal server error |'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '503':
          description: "Service Unavailable\n\n**The following table lists and describes the error codes applicable**\n| Error Code | Meaning                                       |\n|------------|-----------------------------------------------|\n| AISP-004   |System exception                               |    \n| AISP-005   |Consent terms not found with requested payload |"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
  /aisp/authorize:
    post:
      deprecated: true
      summary: Send Authorized Token Issued by Provider
      description: "<!-- theme: warning-->\n> Deprecated\n>\n> Sunset: 30 May 2026\n- Following the PSUs authorization and confirmation of information sharing with their provider, the provider issues a token\n  that permits access to the PSUs data. \n- This token must be transmitted to J.P. Morgan to complete the account information\n  request and digitally sign the request payload."
      tags:
      - AIS
      operationId: createAuthorization
      parameters:
      - $ref: '#/components/parameters/ContentType'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/AuthorizeRequest'
            examples:
              ExampleAuthorizeRequest:
                $ref: '#/components/examples/AuthorizeRequestExample'
        required: true
      x-examples:
      - name: ExampleAuthorizeRequest
        description: Example Authorize Request
        parameters:
          body:
            customerId: TestCustomer1
            providerCode: fake_oauth_client_xf
            authToken: access_token=bc4521d3&state=Pd8b4d0eb
      responses:
        '200':
          description: Successful
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AuthorizeResponse'
              examples:
                ExampleAuthorizeResponse:
                  $ref: '#/components/examples/AuthorizeResponseExample'
        '400':
          description: 'Bad Request.


            **The following table lists and describes the error codes applicable**

            | Error Code | Meaning                                                                                              |

            |------------|------------------------------------------------------------------------------------------------------|

            | AISP-001   |Values are missing for properties: `<properties>`                                                     |

            | AISP-002   |Invalid consent scopes: `<invalid_scopes>`                                                            |

            | AISP-003   |Invalid JSON format                                                                                   |

            | AISP-006   |Report not found with requested payload                                                               |

            | AISP-007   |Customer did not consent to the Provider:<invalid_payload>                                            |

            | AISP-008   |Provider not found for country code: `<invalid_country_code>` or provider code:`<invalid_provider_code>` This error code will appear if an incorrect providerCode is given|

            | AISP-010   |ClientID not present in the header                                                                    |

            | AISP-012   |Required properties are missing: `<missing_fields>`                                                   |

            | AISP-013   |Invalid properties exist: `<additional_fields>`                                                       |

            | AISP-014   |Providers are not available with countryCode: `<country_code>`                                        |

            | AISP-015   |Consent expired, please call consent provider API to re-consent                                       |

            | AISP-016   |Bad request                                                                                           |

            | AISP-017   |The consent has already been revoked                                                                  |

            | AISP-017   |Refresh is not possible because the consent has expired                                               |

            | AISP-017   |A consent with such an id does not exist                                                              |

            | AISP-017   |Refresh is not possible because the consent has been revoked                                          |

            | AISP-017   |The value of consent scopes parameter is invalid                                                      |

            | AISP-017   |The value of consent scopes parameter is not allowed for the client or/and by the provider            |

            | AISP-017   |The next refresh attempt will be allowed according to next_refresh_possible attribute or connection''s status is inactive|

            | AISP-017   |The client tried to connect, reconnect or fetch a connection, but it appears to be disabled           |

            | AISP-017   |Bad requestWe could not find a connection with the requested connection_id                            |

            | AISP-017   |We have received an invalid Date format                                                               |

            | AISP-017   |The passed from_date - to_date interval is out of consent from_date - to_date range                   |

            | AISP-017   |Sending a date value that does not fit in admissible range                                            |

            | AISP-017   |We have received an invalid DateTime format                                                           |

            | AISP-017   |Sending a datetime value that does not fit in admissible range                                        |

            | AISP-017   |The value of fetch_scopes parameter is invalid                                                        |

            | AISP-017   |Fetching holder_info for this provider is not supported                                               |

            | AISP-017   |Invalid consent from_date value, either out of range or a wrong date format                           |

            | AISP-017   |Invalid consent period_days value or not allowed by provider                                          |

            | AISP-017   |Invalid from_date value, either out of range or wrong date format                                     |

            | AISP-017   |Invalid to_date value, either out of range or wrong date format                                       |

            | AISP-017   |We have received some other request format instead of JSON, or the body could not be parsed           |

            | AISP-017   |The accessed provider has the disabled status. Hence, is no longer supported                          |

            | AISP-017   |The requested provider has the inactive status. That means that new connections cannot be created while the current ones cannot be refreshed or reconnected|

            | AISP-017   |Sending a provider_code that is not present in our system                                             |

            | AISP-017   |The connection''s provider has no interactive step                                                     |

            | AISP-017   |Too many connections are being processed at the same time from one application                        |

            | AISP-018   |Customer did not consent to provider `<provider_code>`, please call consent provider API to re-consent|

            | AISP-019   |Provider `<provider_code>` does not support the requested service                                     |'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              examples:
                InvalidJSONFormatExample:
                  $ref: '#/components/examples/InvalidJSONFormatExample'
        '500':
          description: 'Internal server error


            **The following table lists and describes the error codes applicable**

            | Error Code | Meaning              |

            |------------|----------------------|

            | AISP-020   |Internal server error |'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '503':
          description: "Service Unavailable\n\n**The following table lists and describes the error codes applicable**\n| Error Code | Meaning                                       |\n|------------|-----------------------------------------------|\n| AISP-004   |System exception                               |    \n| AISP-005   |Consent terms not found with requested payload |"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
  /aisp/accounts:
    post:
      deprecated: true
      summary: Request for Account Information
      description: "<!-- theme: warning-->\n> Deprecated\n>\n> Sunset: 30 May 2026\n- This request retrieves the account information for a given combination\nof PSU and Provider. \n- An active authorization token is required or access will be denied"
      tags:
      - AIS
      operationId: retrieveAccountInfo
      parameters:
      - $ref: '#/components/parameters/ContentType'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/AccountsRequest'
            examples:
              ExampleAccountsRequest:
                $ref: '#/components/examples/AccountsRequestExample'
        required: true
      x-examples:
      - name: ExampleAccountsRequest
        description: Example Accounts Request
        parameters:
          body:
            customerId: TestCustomer1
            providerCode: fake_oauth_client_xf
      responses:
        '200':
          description: Successful
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AccountsResponse'
              examples:
                ExamplesAccountsResponse:
                  $ref: '#/components/examples/AccountsResponseExample'
        '400':
          description: 'Bad Request.


            **The following table lists and describes the error codes applicable**

            | Error Code | Meaning                                                                                              |

            |------------|------------------------------------------------------------------------------------------------------|

            | AISP-001   |Values are missing for properties: `<properties>`                                                     |

            | AISP-002   |Invalid consent scopes: `<invalid_scopes>`                                                            |

            | AISP-003   |Invalid JSON format                                                                                   |

            | AISP-006   |Report not found with requested payload                                                               |

            | AISP-007   |Customer did not consent to the Provider:<invalid_payload>                                            |

            | AISP-008   |Provider not found for country code: `<invalid_country_code>` or provider code:`<invalid_provider_code>` This error code will appear if an incorrect providerCode is given|

            | AISP-010   |ClientID not present in the header                                                                    |

            | AISP-012   |Required properties are missing: `<missing_fields>`                                                   |

            | AISP-013   |Invalid properties exist: `<additional_fields>`                                                       |

            | AISP-014   |Providers are not available with countryCode: `<country_code>`                                        |

            | AISP-015   |Consent expired, please call consent provider API to re-consent                                       |

            | AISP-016   |Bad request                                                                                           |

            | AISP-017   |The consent has already been revoked                                                                  |

            | AISP-017   |Refresh is not possible because the consent has expired                                               |

            | AISP-017   |A consent with such an id does not exist                                                              |

            | AISP-017   |Refresh is not possible because the consent has been revoked                                          |

            | AISP-017   |The value of consent scopes parameter is invalid                                                      |

            | AISP-017   |The value of consent scopes parameter is not allowed for the client or/and by the provider            |

            | AISP-017   |The next refresh attempt will be allowed according to next_refresh_possible attribute or connection''s status is inactive|

            | AISP-017   |The client tried to connect, reconnect or fetch a connection, but it appears to be disabled           |

            | AISP-017   |Bad requestWe could not find a connection with the requested connection_id                            |

            | AISP-017   |We have received an invalid Date format                                                               |

            | AISP-017   |The passed from_date - to_date interval is out of consent from_date - to_date range                   |

            | AISP-017   |Sending a date value that does not fit in admissible range                                            |

            | AISP-017   |We have received an invalid DateTime format                                                           |

            | AISP-017   |Sending a datetime value that does not fit in admissible range                                        |

            | AISP-017   |The value of fetch_scopes parameter is invalid                                                        |

            | AISP-017   |Fetching holder_info for this provider is not supported                                               |

            | AISP-017   |Invalid consent from_date value, either out of range or a wrong date format                           |

            | AISP-017   |Invalid consent period_days value or not allowed by provider                                          |

            | AISP-017   |Invalid from_date value, either out of range or wrong date format                                     |

            | AISP-017   |Invalid to_date value, either out of range or wrong date format                                       |

            | AISP-017   |We have received some other request format instead of JSON, or the body could not be parsed           |

            | AISP-017   |The accessed provider has the disabled status. Hence, is no longer supported                          |

            | AISP-017   |The requested provider has the inactive status. That means that new connections cannot be created while the current ones cannot be refreshed or reconnected|

            | AISP-017   |Sending a provider_code that is not present in our system                                             |

         

# --- truncated at 32 KB (75 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/jp-morgan-chase/refs/heads/main/openapi/jp-morgan-chase-ais-api-openapi.yml