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

Webhooks API

Set up and manage webhook subscriptions to receive real-time notifications about key events, like transactions, account changes, or client onboarding, directly to your platform, so you can automate workflows and respond instantly as events happen. This API lets you create, update, and monitor your webhook endpoints, giving you fine-grained control over which events you track and how you handle them.

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

This API exposes 4 operations across 2 paths, and defines 79 schemas. It is described by OpenAPI 3.2.0, at version 1.0.55.

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

4 operations 2 paths 79 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.55
Base URL
https://api.payments.jpmorgan.com/embedded/v1
Contact
JPMC Technical Services Support
Resource Areas
1

Paths & Operations 4

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

Webhooks 4

Create and manage webhook subscriptions for your platform.

GET
/webhooks
List webhooks
listWebhooks 2 params → 200400401403404500503
POST
/webhooks
Create a webhook subscription
createWebhook body → 201400401403404500503
GET
/webhooks/{id}
Get a webhook subscription by ID
getWebhook 1 param → 200400401403404500503
POST
/webhooks/{id}
Update a webhook by ID
updateWebhook 1 param body → 200400401403404500503

Schemas 79

The contract defines 79 schemas that model the data the API accepts and returns. The most detailed are TransactionCallbackResource (26 properties), RestrictionsCallbackResource (10 properties), AccountCallbackResource (10 properties), RecipientsCallbackResource (9 properties). Each schema is shown below with its type and property counts.

RoutingInformationItem
object
3 properties 2 required
Context
object
3 properties
TransactionCounterPartyContactDetailsV3
object
Contact details of the counterparty.
4 properties
RestrictionStatusV2
string
Status of the restriction. Can be 'ACTIVE' or 'INACTIVE'
PaymentRoutingInformation
object
2 properties
TransactionCounterPartyRegisteredAccountDetailsV3
object
The registered account details of the counterparty.
5 properties
HoldAmount
string
Amount to hold
TransactionCounterPartyAccountV3
The account details of the counterparty.
RestrictionsCallbackEvent
AccountCallbackResource
object
10 properties
RoutingInformation
object
3 properties 3 required
RemittanceCallbackEvent
RecipientsCallbackResource
object
9 properties
RestrictionReasonV2
string
Reason for the restriction
EventTypeEnum
string
The event types to be notified of.
DocumentCallbackResource
object
3 properties
AccountTypeForNotification
string
Category of the account
Restrictions
object
7 properties
TransactionCallbackEvent
TransactionCounterPartyExternalAccountV3
object
The external account of the counterparty
2 properties 2 required
TransactionCounterPartyRegisteredAccountV3
object
The registered account of the counterparty
2 properties 2 required
AccountStateForNotification
string
State of the account. An account in a state of OPEN can be used for any enabled transactions. An account in PENDINGCLOSE can be used for all transactions suppo…
RoutingInformationV3
object
Routing information for the account.
3 properties
RoutingInformationTransactionType
string
Type of transaction.
AccountType
string
Type of bank account.
WebhookUpdateRequest
object
Update a webhook - add, remove subscriptions or change the status of your webhook
4 properties 2 required
ClientCallbackResource
object
7 properties
OriginatingTransactionV3
object
Details of the originating transaction for fees, returns, or linked transactions.
2 properties
WebhookRequest
object
Create a webhook
3 properties 1 required
TransactionCounterPartyAddressDetailsV3
object
The address details of the counterparty.
7 properties 2 required
ChangeDetails
object
Details describing changes required to the recipient. This is only used when eventType is TRANSACTIONCHANGEREQUESTED.
2 properties 2 required
ListWebhookResponse
object
2 properties 2 required
PartyCallbackEvent
StatusDetails
object
StatusDetails
5 properties
Subscription
object
The webhooks you are subscribed to. Each subscription contains events about which you are notified via HTTPS request to your pre-configured server URL.
1 property 1 required
TransactionCounterPartyCardAccountDetailsV3
object
The card details of the counterparty account.
3 properties
OverdraftStatus
object
Details related to the account overdraft status. This is only used when eventType is ACCOUNTOVERDRAWN.
3 properties
TransactionPaymentPurpose
object
The purpose of the payment
2 properties
ApiError
object
5 properties 3 required
PartyCallbackResource
object
3 properties
DocumentCallbackEvent
RestrictionReason
string
Reason for the restriction
AccountCallbackEvent
TransactionCounterPartyDetailsV3
object
The party details of the counterparty.
5 properties
WebhookResponse
object
7 properties 5 required
AuthorizationDetails
object
This object holds additional authorization details to apply when sending webhook notifications.
3 properties
ClientCallbackEvent
WebhookCallbackEventBase
object
5 properties 3 required
PaymentTypeResponseV3
string
The transaction type indicates the nature of the transaction. Certain types cannot be initiated through the API and, as a result, are excluded from the transac…
TransactionCounterPartyCardAccountV3
object
The card account of the counterparty
2 properties 2 required
WebhookCallbackEventType
string
Master list of all webhook callback event types. Resource-specific callback events override this with a narrowed enum.
PageMetaData
object
3 properties
TransactionCallbackResource
object
26 properties
RoutingNumber
string
Routing number corresponding to the routing code type
RoutingCodeType
string
Type of routing code.
GetTransactionCounterPartyV3
object
5 properties
CountryCode
string
Two letter country code based on ISO 3166 standard
AggregateOverdrawn
object
7 properties
TransactionCounterPartyExternalAccountDetailsV3
object
The external account details of the counterparty.
6 properties
RecipientStatus
string
Callback event type needs to send to notsub for correct status.
SigningKey
object
This returns the public key details used to decrypt the webhooks payload
3 properties
CurrencyCode
string
Three letter currency code based on ISO 4217 standard
ApiErrorV2
object
Schema representing a version 2 API error, including title, HTTP status, and additional context.
5 properties 1 required
SecurityPreferences
object
Parent Object which holds information on security preferences for sending Webhook Notifications.
2 properties
Timestamp
string
Date and time
RecipientType
string
WebhookCallbackEvent
RestrictionsCallbackResource
object
10 properties
RestrictionType
string
Restriction type
CorrectedValue
object
2 properties 2 required
RecipientsCallbackEvent
RecipientAccount
object
Bank account details of the recipient.
5 properties 2 required
RestrictionStatus
string
Status of the restriction
AccountNumber
string
Demand Deposit Account number or International Account Number (IBAN).
TransactionCounterPartyIdentityDetailsV3
object
Identity details for the counterparty.
2 properties
ResourceObjectType
string
RestrictionTypeV2
string
The type of restriction to apply to the account, Can be 'DEBITS', 'CREDITS', 'DEBITCREDIT', 'DIRECTDEBIT' or 'HOLD'
RemittanceCallbackResource
object
5 properties
ApiErrorReasonV2
object
Schema representing detailed reasons for an API error, including code, location, and message.
4 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jp-morgan-chase-webhooks-api-openapi.yml Raw ↑

Other APIs JPMorgan Chase publishes across the network.

Notifications API
Accounts API
Recipients API
Transactions API
Documents API
JPMorgan Chase Account Information API
JPMorgan Chase Account Restrictions API
JPMorgan Chase Account Services API
JPMorgan Chase Account Statements API
JPMorgan Chase Account Transactions API
JPMorgan Chase Account Updates API
JPMorgan Chase Account Validation API
Where this information came from

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