Please bookmark this page and check back often for the latest updates.

Testing Instructions

This section contains technical details regarding secure connections between our clients. Please share this page with the appropriate teams within your organization.

What’s Happening?

Ahead of the migration, self-service connectivity testing will be available in both our User Acceptance Testing (UAT) and Production (PROD) environments. Only connectivity testing is required for this move. Clients will be provided with two options to test connectivity:

  • Initiating an API Call (Recommended): Test the endpoint using existing credentials and validate the connectivity by receiving a successful response of ‘HTTP 200’ Status code.
  • Network cURL Test: Conducting a network cURL test in UAT and PROD environments from the system that currently accesses J.P. Morgan’s APIs. For instructions on network cURL testing, please refer to the steps below:

1. Download the cURL tool and ensure the correct installation for your platform.

2. Use the following commands to test across each environment:

For testing Mutual TLS connectivity

UAT: cURL " “-X GET --header "Accept:application/json" --cert Transport_UAT_Cert.crt (replace with exact certificate name) --key Transport_UAT.key.pem(replace with exact certificate name)

PROD: cURL " "-X GET --header "Accept: application/json" --certTransport_PROD_Cert.crt (replace with exact certificate name) --key Transport_PROD.key.pem(replace with exact certificate name)

For testing OAuth connectivity

UAT: cURL " " [SS(G2] -X GET --header "Accept:application/json" -X GET --header "Authorization: Bearer<token>"

PROD: cURL " "-X GET --header "Accept: application/json" -X GET --header"Authorization: Bearer <token>"

3. Confirm successful connection to the new Data Center by emailing including your Access Profile ID in the subject of the email and attaching a screenshot of connection validation.

Sample Success Response:
* using HTTP/1.x
> GET /tsapi/v1/connect HTTP/1.1
> Host:
> User-Agent: curl/8.1.2
> Accept: application/json

< HTTP/1.1 200 OK
< Date: Fri, 05 Jan 2024 19:25:21 GMT
< Content-Type: application/json
< Connection: keep-alive
< Strict-Transport-Security:max-age=63072000; includeSubdomains; preload
< X-Frame-Options: SAMEORIGIN
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1; mode=block
< Vary: Accept-Encoding
< Transfer-Encoding: chunked
< Set-Cookie:ppnet_443=!
0rZVIjwugCYIJ4Sb6a6YvQ00svN1q6IU4xbzs5skJDTiG4Y4GFhrD0GPzYJLk1E4ybIUrTxDP6pHYg==;path=/; Httponly; Secure

{"status": “Success”,“Environment”: “UAT”}

To ensure technical specifications and guidance remains accurate, please do not translate this page into any other language.


If you have any questions or require assistance, please contact with specific details pertaining to your questions.