Tamr can publish notifications for these events to a user-specified endpoint (a webhook):
- Golden record events including update delete, merge, unmerge, and enrich events.
- Platform events
- User authentication events including user login and password changes.
- User authorization events when a user attempts to access Tamr Cloud resources.
- Job events when a job state changes.
The notifications are published as HTTPS POST requests. The webhook receives these requests and sends messages with the event data to a subscribing application or portal. For example, when a new record is created in the SOR, Tamr publishes a notification to the specified webhook, which then sends the CREATE event to a consumer application such as a CRM.
Webhook Requirements and Configuration
See Configuring Webhooks for client webhook requirements, integration requirements, and configuration instructions.
You can pause and replay webhook events as needed. See Configuring Webhooks for more details and instructions.
Webhook Payload Format
Webhook payloads follow the CloudEvents standard. CloudEvents is a specification for describing event data in a common format to provide interoperability across services, platforms and systems. The CloudEvents specification defines a standard envelope for event data. For ease of adoption, CloudEvents SDKs are available in a variety of languages.