.png)
Reltio Integration Guide
Reltio integrates with enterprise systems through REST APIs, event-oriented notifications, bulk processing, and OAuth-secured data synchronization.
Reltio integration options at a glance
Reltio’s primary integration mechanism is its REST API, which supports mastered entities, relationships, search, metadata, matching, merging, tenant operations, interactions, and related data services. Reltio also supports event-oriented and outbound integration capabilities for selected changes, although coverage and delivery methods depend on the configured capability. Bulk and asynchronous operations support initial loads, exports, and high-volume synchronization, with job-status polling often required. File-based exchanges can support relevant bulk workflows, but a general-purpose attachment API was not confirmed. Martini can consume these APIs, receive compatible callbacks, orchestrate jobs, transform JSON, schedule reconciliation workflows, and securely manage OAuth credentials.
| Integration point | Supported by Reltio? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Reltio REST APIs support entities, relationships, search, metadata, matching, merging, interactions, tenant operations, and related data services. They are the primary interface for current programmatic integrations. | Martini can consume authenticated Reltio REST endpoints from workflows, map JSON responses, apply business rules, and expose a controlled REST API façade for downstream applications. |
| Webhooks / outbound callbacks | Limited | Reltio supports event-oriented and outbound integration patterns for selected entity changes, match and merge outcomes, and other configured platform activity. Delivery may be through a callback, streaming mechanism, or supported integration service rather than a universal webhook. | Martini can receive compatible HTTP notifications through an API or webhook-consuming workflow, validate event identity and tenant context, retrieve current Reltio data, and process duplicates safely. |
| Bulk / async / batch APIs | Yes | Bulk loading, exporting, and asynchronous processing support initial loads, high-volume updates, periodic synchronization, and reprocessing after data-quality or model changes. | Martini can submit a bulk job, persist its identifier, poll for completion, retrieve pages or files, transform batches, and route rejected or failed items for recovery. |
| File import/export | Limited | File-based exchanges are relevant to bulk import and export workflows. A general-purpose Reltio attachment API was not confirmed. | Martini can process supported exported or bulk-load files and combine file handling with validation, transformation, batching, and downstream delivery without assuming attachment semantics. |
| Authentication | Yes | Reltio uses OAuth 2.0 bearer tokens with client-credential or application-based authentication, tenant-specific access, and authorization through roles, permissions, and data-access policies. | Martini can store client credentials and tenant configuration in secrets or protected environment configuration and use bearer-token authentication in REST workflows. |
| Scheduled synchronization | Yes | Scheduled queries, exports, and reconciliation jobs can complement event-driven integration for unsupported event types, historical backfills, and periodic validation. | Martini can trigger workflows on a schedule, persist synchronization markers, query incrementally where supported, and coordinate bounded reconciliation workloads. |
| Database / analytics access | Not confirmed | A direct customer-facing SQL interface to Reltio’s operational store was not confirmed. Analytics or data-lake delivery may depend on subscription and separately deployed products. | Martini should use documented Reltio APIs, exports, or supported data-delivery services rather than assuming direct database access. |
How Reltio exposes data and business events
Reltio REST APIs
Reltio REST APIs are the primary programmatic interface for entities, relationships, search, metadata, interactions, matching, merging, tenant operations, and related data services. They support both synchronous retrieval and submission of operations that may be processed asynchronously.
Martini implementation pattern
Martini implementation pattern: a workflow authenticates with an OAuth bearer token, calls the required Reltio endpoint, handles pagination or asynchronous job responses, maps the returned JSON, applies validation and business rules, and writes the result to the target system or an integration store.
Implementation sequence
Reltio Events and callbacks
Reltio supports event-oriented and outbound integration capabilities for selected entity changes, match and merge outcomes, and other platform activity. Event coverage, delivery method, and ordering depend on the configured capability, so every event type should be verified before implementation.
Martini implementation pattern
Martini implementation pattern: expose a controlled API or webhook workflow for compatible HTTP callbacks, validate the event identifier, tenant, source, timestamp, and entity URI, then retrieve current Reltio data before applying an idempotent downstream update. For streaming or non-HTTP delivery, use the supported delivery path and preserve the same validation and retry principles.
Implementation sequence
Reltio Bulk and asynchronous APIs
Reltio bulk and asynchronous capabilities support initial loads, large entity updates, exports, periodic synchronization, and reprocessing. Operations can require job submission, status polling, output retrieval, and separate handling for rejected records.
Martini implementation pattern
Martini implementation pattern: orchestrate the complete job lifecycle in a workflow, persist the job identifier and status, poll with bounded retries, process output pages or files in batches, and distinguish transport errors from validation and data-quality failures.
Implementation sequence
Reltio File import and export
Reltio data exchanges can involve files for relevant bulk-load and export workflows. This path should not be treated as a general-purpose attachment interface because a universal attachment API was not confirmed.
Martini implementation pattern
Martini implementation pattern: receive or retrieve the supported file output, parse its documented format, validate rows or objects against the tenant model, transform the data, and route valid batches to target APIs while retaining rejected items and processing metadata.
Implementation sequence
Common Reltio integration patterns
Pattern 1: Synchronize mastered customers to a CRM
When to use this pattern
Use this pattern when Reltio governs customer Organizations and Individuals and Salesforce must reflect the current mastered profile. Event-driven processing can provide lower latency where the required Reltio event is available, while scheduled incremental queries provide a reconciliation path.
Integration direction
Example Mapping
| Reltio Field | Canonical Field | Target Field |
|---|---|---|
| Entity URI | masterId | External ID |
| Name attributes | legalOrDisplayName | Account Name or Contact Name |
| Crosswalk identifiers | sourceSystemIds | Source System ID |
| Relationship attributes | accountContactRelationship | Account-Contact association |
Martini implementation pattern
Martini receives a supported notification or retrieves changed entities, fetches the complete mastered payload, normalizes nested attributes and crosswalks, applies eligibility and merge rules, and performs an idempotent Salesforce upsert. Transient failures are retried with backoff, while validation and duplicate failures are routed for review.
Martini capabilities used
- workflows
- API consumption
- data mapping
- business rules
- error handling
- scheduled execution
Pattern 2: Distribute mastered organizations to an ERP
When to use this pattern
Use this pattern when Reltio is the governed source for organizations, suppliers, customers, products, or Locations consumed by SAP or NetSuite. It is useful for enforcing consistent identifiers and validation before ERP updates.
Integration direction
Example Mapping
| Reltio Field | Canonical Field | Target Field |
|---|---|---|
| Entity type | partyType | Customer or supplier type |
| Address attributes | locations | ERP address or location |
| Crosswalk identifiers | externalReferences | ERP external ID |
| Operational status | masterStatus | ERP lifecycle status |
Martini implementation pattern
A Martini workflow retrieves Reltio data through REST APIs or a scheduled export, validates required ERP fields, converts nested JSON to the target schema, and submits the update. Response identifiers and statuses are persisted for reconciliation, and failed batches are separated into retryable transport errors and permanent validation errors.
Martini capabilities used
- workflows
- API consumption
- data transformation
- validation
- business rules
- retry handling
Pattern 3: Propagate match and merge outcomes
When to use this pattern
Use this pattern when downstream applications must respond to Reltio survivorship or merge decisions. It prevents duplicate downstream customers and ensures records associated with deprecated source references are redirected or consolidated.
Integration direction
Example Mapping
| Reltio Field | Canonical Field | Target Field |
|---|---|---|
| Surviving Entity URI | survivingMasterId | Primary downstream record |
| Deprecated crosswalk | retiredSourceId | Merged or redirected record |
| Merge event identifier | governanceEventId | Audit reference |
| Relationship changes | updatedAssociations | Downstream relationship set |
Martini implementation pattern
Martini receives or detects a match or merge outcome, retrieves the surviving entity and relevant crosswalks, determines the downstream records affected, and applies idempotent merge, retire, or redirect logic. The workflow records the governance event and retries only operations that can safely be repeated.
Martini capabilities used
- event-driven workflows
- API consumption
- data mapping
- business rules
- idempotency
- audit logging
Pattern 4: Run a bulk reconciliation and migration
When to use this pattern
Use this pattern for initial population, high-volume synchronization, historical backfills, or reconciliation after a Reltio data-model or quality change. Bulk processing is preferable to issuing one request per entity at large scale.
Integration direction
Example Mapping
| Reltio Field | Canonical Field | Target Field |
|---|---|---|
| Entity attributes | masteredEntity | Curated entity dataset |
| Relationships | entityRelationships | Relationship table |
| Crosswalks | sourceLineage | Source-reference columns |
| Match and merge metadata | dataQualityOutcome | Quality and survivorship dataset |
Martini implementation pattern
Martini submits and monitors the Reltio export or bulk job, retrieves pages or files, validates and transforms records in bounded batches, and loads the target platform. Job identifiers, checkpoints, rejected items, and retry state are persisted so a partial failure does not require an uncontrolled restart.
Martini capabilities used
- scheduled workflows
- asynchronous orchestration
- file processing
- data mapping
- batch processing
- error handling
Applications commonly integrated with Reltio
Reltio is commonly positioned as a mastered-data layer between source systems and consuming enterprise applications. The following products represent practical integration targets or sources; exact ownership, object mappings, event coverage, and delivery methods should be confirmed for each tenant and subscription.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Synchronize mastered Organizations, Individuals, customer identifiers, and relationships with CRM Accounts and Contacts. | Reltio → Martini → Salesforce | Martini can receive a supported Reltio event or run an incremental query, retrieve the complete mastered entity, map attributes and crosswalks, and upsert Salesforce records using stable correlation keys. Retryable failures can be routed for replay or review. |
| SAP | Distribute mastered customers, suppliers, products, and Locations to ERP processes while retaining operational identifiers where required. | Reltio → Martini → SAP | A Martini workflow can retrieve Reltio entities, validate required attributes, transform nested JSON into SAP’s target structure, call the relevant SAP API, and persist response identifiers and status for reconciliation. |
| ServiceNow | Keep organization, contact, customer, and location information consistent for service management and operational workflows. | Reltio → Martini → ServiceNow | Martini can consume Reltio REST data or selected event notifications, map mastered entities and relationships to ServiceNow objects, apply ownership and validation rules, and handle duplicate or transient failures through controlled retries. |
| Workday | Exchange mastered organizations, workers, Locations, or reporting relationships when Reltio participates in the enterprise data-governance model. | Workday → Martini → Reltio | Martini can retrieve source data from Workday, normalize it into the Reltio entity model, validate tenant-specific attributes and relationship types, and submit changes through Reltio REST APIs while preserving source references. |
| Marketo | Align marketing audiences and account or contact attributes with mastered customer data. | Reltio → Martini → Marketo | Martini can select eligible mastered Individuals or Organizations, transform attributes into Marketo’s import or API model, apply consent and eligibility rules, and record delivery outcomes for later reconciliation. |
| Snowflake | Deliver mastered entities, relationships, history, and data-quality outputs to an analytical environment. | Reltio → Martini → Snowflake | Martini can orchestrate a Reltio export or bulk operation, poll for completion, process returned pages or files, normalize nested structures, and load curated datasets into Snowflake through the approved target interface. |
| Databricks | Provide mastered customer or product data for data science, analytics, and downstream data products. | Reltio → Martini → Databricks | Martini can coordinate Reltio bulk exports or supported data-delivery workflows, validate and transform the output, and deliver batches to Databricks while separating rejected items from transport failures. |
| NetSuite | Synchronize mastered Organizations, customers, contacts, and Locations with ERP records and identifiers. | Reltio → Martini → NetSuite | A Martini workflow can query or receive Reltio changes, map the mastered model to NetSuite’s API payloads, apply required-field and duplicate checks, and synchronize target identifiers back to an integration store or Reltio where appropriate. |
How to build a Reltio integration in Martini
Objective
Establish tenant-scoped access to Reltio and configure the target system without embedding credentials in workflow definitions.
Instructions in Martini
- Create protected Martini secrets or environment configuration for Reltio OAuth client credentials and tenant identifiers.
- Configure the target application credentials and endpoint settings separately by environment.
- Use least-privilege Reltio roles, permissions, and data-access policies.
Objective
Select an event, callback, scheduled query, or bulk job trigger based on required latency, object coverage, and volume.
Instructions in Martini
- Use a compatible Reltio event or callback when the required change type is confirmed.
- Use a scheduler for incremental polling, reconciliation, backfills, and unsupported event types.
- Use bulk or asynchronous operations for initial loads and high-volume processing.
Objective
Obtain the complete current Reltio object rather than relying on an event notification that may contain only partial information.
Instructions in Martini
- Validate event type, tenant, entity URI, source, timestamp, and event identifier.
- Call the relevant Reltio REST endpoint with documented filters and pagination.
- Persist event identifiers, job identifiers, timestamps, or other synchronization checkpoints.
Objective
Coordinate retrieval, transformation, target delivery, status polling, and recovery as a maintainable Martini workflow.
Instructions in Martini
- Separate event processing, scheduled reconciliation, and bulk-job orchestration when their operational requirements differ.
- Use bounded parallelism and queues or asynchronous execution where volume requires it.
- Keep transport, validation, data-quality, and business failures distinguishable.
Objective
Convert Reltio’s tenant-specific nested JSON model into a canonical and target-specific representation.
Instructions in Martini
- Map Entities, Relationships, Interactions, Attributes, Crosswalks, and merge metadata explicitly.
- Normalize identifiers and preserve source lineage for idempotent correlation.
- Validate required fields, nested structures, lookup values, and target data types.
Objective
Enforce data-governance and target-system rules before writing mastered data downstream.
Instructions in Martini
- Apply eligibility, ownership, survivorship, consent, and lifecycle rules appropriate to the integration.
- Treat match and merge outcomes as governance events rather than ordinary updates.
- Avoid creating downstream records when a stable entity or crosswalk identifier already exists.
Common Reltio data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Entities | Mastered business objects such as Individuals, Organizations, Products, Locations, and other tenant-specific domain objects, including attributes, identifiers, crosswalks, match information, and operational metadata. | Salesforce, SAP, ServiceNow, Workday, NetSuite, Snowflake, and Databricks | Martini retrieves or receives entity changes, validates tenant-specific metadata, maps nested attributes and identifiers, applies business rules, and upserts or exports the result using stable entity URIs and crosswalks. |
| Relationships | Connections such as ownership, employment, household, organizational hierarchy, and account-contact associations. | Salesforce, SAP, ServiceNow, Workday, and analytical platforms | Martini maps relationship types and endpoints to target associations, checks that referenced entities exist, and processes relationship changes independently where the target model requires it. |
| Interactions | Customer engagement, service, sales, communication, and other business interactions associated with entities. | Salesforce, Marketo, ServiceNow, Snowflake, and Databricks | Martini transforms interaction attributes into target activity or analytical structures, applies event or time-window filters, and handles high-volume delivery through batching when appropriate. |
| Attributes | Typed, nested, or complex properties belonging to entities or relationships. | CRM, ERP, marketing, service, and data platforms | Martini maps attribute paths and data types, validates required values and lookups, handles nullability and schema changes, and separates governed fields from operational fields. |
| Crosswalks | Source-system references connecting mastered entities or attributes to contributing-system identifiers. | Salesforce, SAP, Workday, NetSuite, and integration databases | Martini uses crosswalks as correlation keys for idempotent upserts, stores target identifiers where appropriate, and preserves source lineage during synchronization. |
| Matches and merges | Match candidates, survivorship outcomes, merged records, and information about the surviving mastered entity. | Salesforce, ServiceNow, SAP, data warehouses, and audit stores | Martini treats merge outcomes as governance events, identifies the surviving entity and deprecated references, updates downstream identifiers, and records an audit trail. |
Authentication and security considerations
OAuth and tenant access
Reltio integrations use OAuth 2.0 bearer tokens with client-credential or application-based authentication, tenant-specific access, and authorization through Reltio roles, permissions, and data-access policies.
Martini configuration
- Store client credentials, tokens, tenant identifiers, and endpoint configuration in Martini secrets or protected environment configuration.
- Use least-privilege Reltio access and separate credentials by environment.
- Never embed credentials in mappings, source code, workflow definitions, or API responses.
- Mask personal, financial, and other regulated attributes in logs.
Operational considerations for Reltio integrations
Reliability and scale
- Confirm tenant-specific quotas and concurrency limits, and apply backoff for 429 and transient 5xx responses.
- Use documented pagination, filtering, and stable synchronization markers instead of repeatedly retrieving full populations.
- Persist bulk job identifiers and poll asynchronously with bounded retry policies.
- Make processing idempotent with Reltio entity URIs, crosswalk identifiers, and event identifiers.
Data and event behavior
- Validate tenant-specific entity types, attributes, relationship types, lookups, and nested structures as schemas evolve.
- Do not assume uniform event coverage or global event ordering across entities, relationships, interactions, or administrative operations.
- After an event, retrieve current data when notifications are partial or eventual consistency may delay availability.
- Handle match and merge outcomes explicitly and preserve an audit trail for survivorship decisions.
Testing and monitoring
Test authentication, pagination, retries, duplicate delivery, partial bulk completion, rejected records, schema changes, and merge scenarios. Capture the tenant, entity URI, source, request correlation identifier, and Martini workflow execution identifier without logging sensitive payloads.
Why use Martini instead of scripts or point-to-point integrations?
Reusable integration orchestration
Martini provides workflows and APIs for coordinating Reltio calls, event intake, bulk-job polling, target delivery, and reconciliation in one maintainable integration asset.
Controlled transformation
Instead of embedding mappings and business rules in isolated scripts, Martini centralizes transformations for Reltio’s nested JSON, crosswalks, relationships, and merge outcomes. The same logic can be reused across event, scheduled, and bulk flows.
Operational resilience
- Apply consistent authentication, retry, validation, idempotency, and error-routing patterns.
- Separate transport failures from data-quality and business-rule failures.
- Expose controlled APIs for downstream consumers without exposing Reltio credentials or tenant details.
- Monitor workflow executions and retain checkpoints for recovery and reconciliation.
Frequently asked questions
Reltio can be integrated through its REST APIs, configured event-oriented or outbound integration capabilities, bulk and asynchronous operations, and supported file-based import or export workflows. OAuth 2.0 bearer-token authentication, tenant-scoped authorization, pagination, job polling, and idempotent processing are important parts of the design.
Yes. Martini can integrate with Reltio by consuming its REST APIs, receiving compatible Reltio event or callback notifications, orchestrating bulk and asynchronous operations, processing supported files, and running scheduled synchronization workflows. A native Martini Reltio connector was not documented in the supplied sources.
No. A dedicated Reltio connector is not required. Martini can use Reltio’s documented REST APIs, OAuth authentication, supported event or outbound integration mechanisms, bulk capabilities, and file workflows through Martini APIs and workflows.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Reltio. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Reltio, cloud infrastructure, or other third-party systems based on subscription, usage, and deployment model.
Use REST APIs as the primary method for entity, relationship, search, metadata, matching, merging, and tenant operations. Use supported events or callbacks when low-latency change handling is required, and use scheduled queries or bulk and export operations for reconciliation, backfills, and high-volume workloads. No current Reltio GraphQL or SOAP API was confirmed.
Reltio supports event-oriented and outbound integration patterns for selected changes, including entity changes and match or merge outcomes, but coverage and delivery method depend on the configured capability. Martini can receive compatible HTTP callback notifications, while other supported streaming or integration delivery methods should be designed according to the Reltio tenant configuration.
Martini can retrieve or receive Reltio Entities, Relationships, Interactions, Attributes, Crosswalks, and merge information, then map them to canonical and target-specific models. Stable entity URIs, crosswalks, source identifiers, and event or timestamp checkpoints support incremental synchronization and idempotent upserts.
A robust integration classifies authentication, authorization, validation, rate-limit, conflict, not-found, transient server, and permanent business errors separately. Martini can apply bounded retries with backoff for transient failures, detect duplicate event identifiers or stable entity keys, preserve checkpoints, and route unrecoverable items for review. Reltio event ordering and eventual consistency should also be considered.
Related Martini documentation
Martini APIs
Data processing
Security and operations
Related documentation
Review the Reltio API and integration references together with Martini API, workflow, security, mapping, and operational documentation when designing the implementation.