Tamr API
Tamr exposes a full REST API mirroring the UI, plus Connect, data-movement, and RealTime APIs, with a first-party Python SDK. There is no self-serve signup: access comes with an enterprise deployment. Eventing is limited, so most triggering means polling the jobs API.
Frequently asked questions
Tamr scores C on the API Report Card. Tamr exposes a full REST API mirroring the UI, plus Connect, data-movement, and RealTime APIs, with a first-party Python SDK. There is no self-serve signup: access comes with an enterprise deployment. Eventing is limited, so most triggering means polling the jobs API.
Tamr has an official API, but teams routinely hit its limits: gated access, partial coverage, or paid tiers. Most end up supplementing it with exports or an unofficial API layer like Supergood.
Tamr is an AI-native master data management (MDM) and entity-resolution platform that unifies, cleans, de-duplicates, and enriches enterprise data across CRM, ERP, EHR, supplier, product, and location domains so that downstream analytics, operational systems, and AI agents work off a single trusted record.
Primary vertical: misc (horizontal enterprise data infrastructure). A global manufacturer has supplier records spread across SAP S/4HANA, Oracle EBS, Coupa, Ariba, and a dozen regional ERP instances acquired through M&A; the same vendor (e.g., 'Acme Logistics GmbH') appears as 14 different supplier IDs with inconsistent tax IDs, addresses, and parent-company hierarchies.
Medium. Tamr is well-known inside the MDM / data-engineering buying center and is consistently named as a Visionary or Niche Player in Gartner's MDM Magic Quadrant alongside Reltio, Informatica, Profisee, Semarchy, Ataccama, SAP MDG, and Stibo.
Tamr is the system of reference for 'who is the real customer / supplier / provider / product' across an enterprise.
Tamr launched in 2013 as the commercialization of MIT's Data Tamer research and was one of the first MDM vendors to lead with supervised machine learning instead of deterministic rules and survivorship.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.