Developer Programs
Getting Started
Get started working with Jack Henry's developer programs today.
Fintech Integration Network (FIN)
Jack Henry's Integration Program for Fintechs.
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.
Digital Core
Modernize with cloud-native core banking technology.
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.
Full List of APIs
Begin working with Jack Henry's public APIs to build financial applications today.
jXchange REST-Legacy Migration announced. Deadline for migration is July 31, 2026.
More info

Find Alert Recipient

Tutorials > Enterprise Notification System (ENS) > Find Alert Recipient

I need to find out if a customer is enrolled as an Alert Recipient.

Steps

  1. The user inserts the customers name or part of it and performs a NotRecipSrch and response has the ConsmRecipId and the AlrtRecipId.
  2. The information from the search response can be used in the NotRecipInq.
  • Note: It is confusing with both NotRecip and NotRecipSub operations. The difference is While both searches return the ConsmReciptID, NotRecipSrch returns the AlrtRecipId whereas NotRecipSubSrch returns whether the recipient is active for subscriptions.

NotRecipInq returns the recipient contact information records (WorkEmail and SMSNative) whereas NotRecipSubInq returns the subscriptions.

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

Have a Question?
Did this page help you?
Last updated Wed Mar 4 2026