Developer Programs
Vendor Integration Program (VIP)
Direct access to Jack Henry's technical integration resources.
Technical Account Manager (TAM)
Get technical integration help from a single point of contact.
Developer Account
Create a developer acccount to access resources that help you integrate with Jack Henry.
Learn
Shared Responsibility
Learn about shared roles and responsibilities of customers and Jack Henry in open banking.
Developer Use Cases
Find a use case that fits your development needs.
Developer Video Gallery
Watch the latest demos, webinars, and more.
Developer Conference
Connect with industry leaders, gain insights from expert speakers, and explore our latest innovations.
Docs
Admin API
Create solutions for an institution's back office support tools.
Authentication Framework
Map customer identities to your existing system IDs.
Consumer API
Access financial data for user accounts, transactions, and more.
Data Hub
Get deeper access to financial institution data.
Enterprise Event System
Respond to events in real-time using this powerful pub/sub-based solution.
jXchange - REST API
Translate business information between Jack Henry and 3rd-party apps using a REST-based API.
jXchange - SOAP API
Translate business information between Jack Henry and 3rd-party apps using a SOAP-based API.
Operational Data Integration (ODI)
Get customized queries for bulk data needs.
Payments
Embed check deposits, ACH, bill pay, cards, and real-time payments.
Plugin Framework
Embed the best of the fintech world directly into your user's dashboard.
SymXchange
Query Symitar core member accounts, post transactions, run PowerOn scripts, and more.
Xperience
Modern UI that provides consistent visual integration across Jack Henry products.
Full List of APIs
Begin working with Jack Henry's public APIs to build financial applications today.
The security model enhancement for jXchange SOAP APIs begins on May 1st, 2025.
More info

Modify Alert Recipient

Enterprise SOAP API > Tutorials > Enterprise Notification System (ENS) > Modify Alert Recipient

The bank teller needs to modify or delete a recipient alert.

Steps

  1. The user inserts the customer’s name or part of it and performs a NotRecipSrch and the response has the ConsmRecipId and the AlrtRecipId.
  2. The response information is used in the NotRecipInq to obtain the AlrtRecipId, ConsmRecipId, and ActIntentKey.
  3. Using the InstRtId, ConsumerProd, AlrtRecipId, ConsmRecipId and ActIntentKey, the user can utilize the NotRecipMod operation to modify the subscription. To delete the recipient’s subscription set the <Dlt> element to true.

Referenced and Associated Operations

Detailed information about the operation, the request structure/response, error messages and other useful information can be obtained by clicking the operation name below.

Operation NameDescriptionXSD/WSDL Container
NotRecipSrchSearch for specified recipientENS
NotRecipInqInquire for recipient contact informationENS
NotRecipModModify or delete the recipientENS
Have a Question?
Have a how-to question? Seeing a weird error? Get help on StackOverflow.
Register for the Digital Toolkit Meetup where we answer technical Q&A from the audience.
Did this page help you?
Last updated Thu Jul 14 2022