look up and manage constituent records via the tessitura rest api
domain: tessitura.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with the org's TessituraService Basic Auth credentials as with other Tessitura REST calls.
Use the constituent resources to look up or create constituent (patron) records — Tessitura's CRM model treats ticketing, fundraising, and membership as facets of one constituent.
Search by known identifiers (e.g. email, constituent ID) rather than broad queries, since constituent data is sensitive personal information.
Respect your organization's data governance rules before writing back to constituent records, since Tessitura is the system of record for many arts organizations' CRM data.
Confirm field-level permissions with your Tessitura administrator, since access is typically scoped by the group/location embedded in your credential.
Known gotchas
Constituent records unify ticketing, donor, and membership data — an integration built only for 'customers' may unexpectedly touch fundraising/membership fields too.
Access is scoped by the group/location in your Basic Auth credential, so a valid login for one department may not see records visible to another.
As with the rest of the Tessitura API, full documentation is only available to registered developers via your organization's account, not a public doc site.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?