Cuseum - Tessitura Integration Follow

Technical details and instructions related to Cuseum’s Tessitura integration.
[A] Tessitura API Access:
In order for our system to connect and communicate with Tessitura, we’ll need access on the API level.
Step A-1.
Please create a user for Cuseum that is of the “API” user type.
Make sure you assign the API user to the appropriate User Group.

Step A-2.
Provide Cuseum with the full Tessitura API Authentication String
The Tessitura API Authentication String is composed of Username, GroupID, Location, and Password.
(e.g. RestWeb2:admin:RestWeb2:Password123)
💡Need more help? Refer to Tessitura’s video on “Part 2: API User Configuration”
https://www.tessituranetwork.com/en/Items/Videos/Training/API/Tessitura_API

Step A-3.
Provide Cuseum with your Tessitura API URL.
If you’re leveraging Tessitura’s RAMP hosting, the URL might look something like this:
https://yourname.tessituranetworkramp.com/LiveAPI/TessituraService/
or https://yournamerestprod.tnhs.cloud/tessituraservice/
If you have a self-hosted environment, the URL might look something like this:
https://tessexternal.yourname.org/TessituraService/ (but, ultimately, your IT network would know)

[B] Tessitura software/interface Access:
Now that you’ve granted Cuseum API access, we also need to ensure we have access at the software/interface level.

Step B-1.
Please create an Admin user for Cuseum so that we can access the Tessitura software.
This will enable us to help you during set-up, testing, and troubleshooting. We’ll need to know the username,
password, and any other details required to access your Tessitura instance the same way you do on the day-to-day.

Step B-2.
Create a “List” and send Cuseum this specific List ID.
This will act as the query/criteria of the members you’d like our system to fetch from Tessitura.

With there being different types of configurations and layers of security, here are some other aspects for your review and consideration. Please note that they may or may not be applicable to your set-up.

Whitelist Cuseum’s IP addresses.
If you’re self-hosted and have high-levels of security around accessing the server you use to host Tessitura, we will request that you whitelist 2-4 Cuseum IP addresses.

Provide Cuseum with Citrix credentials.
Some instances of Tessitura require us to log-in via Citrix. Citrix, as a tool to access the VPN, has a separate username
and password than the Tessitura software, and often includes a device token or DUO Mobile to generate an access code on-demand.

What API endpoints does Cuseum use?
Cuseum’s system uses GET request to read data from Tessitura on these endpoints:
- Reporting/Lists/XXXX/Contents
- CRM/Constituents/:id
- CRM/ContactPoints?constituentId=XXX
- CRM/Memberships/Details?constituentId=XXX
Note: These are the GET requests our integration uses. If your data/lists are structured, further filtered, or modified in a different way (e.g. using
Output Sets, additional parameters), please inform us in advance, as additional time and fees may apply. Additionally, our system uses REST API,
which is the most up-to-date way of communicating with Tessitura.

Can Cuseum use Test & Production Environments?
Depending on your process and preferences, Cuseum can work from a Test Environment first, and then change to a Live/Prod environment after successful integration testing with your Test Environment.