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

Validation Services API

Verify accounts and identities for individuals and organizations in real time, so you can confidently onboard customers, reduce fraud, and meet compliance requirements with a single, streamlined integration.

Validation Services 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 Account Validation and Entity Validation. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 2 paths, organized into 2 resource areas, and defines 22 schemas. It is described by OpenAPI 3.0.1, at version 2.2.3.

Requests are made against 3 base URLs: https://apigateway.jpmorgan.com/tsapi/v2, https://apigatewaycat.jpmorgan.com/tsapi/v2, https://api-mock.payments.jpmorgan.com/tsapi/v2.

2 operations 2 paths 22 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
2.2.3
Base URL
https://apigateway.jpmorgan.com/tsapi/v2
Contact
JPMC Technical Services Support
Resource Areas
2

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 POST. They span 2 resource areas: Entity Validation, Account Validation. Each is listed below with its method, path, parameters, and response codes.

Entity Validation 1

API to validate entities

POST
/validations/entities
Entity validation
entityValidation 3 params body → 200400403429500
Account Validation 1

API to validate accounts

POST
/validations/accounts
Account validation
accountValidation 3 params body → 200400403429500

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are IndividualEntity (17 properties), PostalAddress (13 properties), ResultCollection (11 properties), OrganizationEntity (9 properties). Each schema is shown below with its type and property counts.

Payload
PostalAddress
object
Required for Entity Validation
13 properties 1 required
EntityId
object
5 properties 2 required
Response
object
3 properties
ResponseCollection
object
A collection of validation responses
4 properties
ResponseDetails
object
4 properties
Result
object
4 properties
AccountScore
object
Account score information in coded message format being: | code | message | |-------|----------------------| | 1109 | Information Found | | 1209 | No Informati…
2 properties
ResultCollection
object
11 properties
EntityDetails
object
4 properties 1 required
Individual
object
1 property 1 required
IndividualEntity
object
An individual entity
17 properties 3 required
Organization
object
1 property 1 required
OrganizationEntity
object
9 properties 1 required
Account
object
3 properties 2 required
FinancialInstitutionId
object
3 properties 1 required
PhoneNumber
object
2 properties
PhoneNumbers
array
AccountDetails
object
6 properties 2 required
Transaction
object
3 properties
Amount
object
3 properties
Errors
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jp-morgan-chase-validation-services-api-openapi.yml Raw ↑

Other APIs JPMorgan Chase publishes across the network.

Digital Onboarding API
Consumer Profile Management API
Tokenization API
Reporting API
Notifications API
Request to Pay via QR Code API
Checkout API
Dispute Management API
Accounts API
Alerts and Decisioning API
Product Configuration API
Recipients API
Where this information came from

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