Skip to main content

Reltio

Reltio is a cloud-based master data management (MDM) platform that provides data-driven applications, helping organizations create a single source of truth for their data and build intelligent applications with clean, connected, and contextual data.

Reltio icon

Power end-to-end data operations for your Reltio API with Nexla. Our bi-directional Reltio connector is purpose-built for Reltio, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Reltio or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Reltio workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

Before creating a Reltio credential, you need to obtain your OAuth2 Client ID and Client Secret from your Reltio account. Reltio uses OAuth2 2-legged authentication, which allows Nexla to access your Reltio account using client credentials without user interaction.

To obtain your Reltio OAuth2 credentials, follow these steps:

  1. Sign in to your Reltio account using your administrator credentials.

  2. Navigate to your account settings or API management section in the Reltio interface.

  3. Look for the API or OAuth2 Applications section in your account settings, or navigate to Settings > API or Developers > OAuth2 Applications.

  4. If you don't have an OAuth2 application yet, look for the option to create or register your OAuth2 application.

  5. Click Create OAuth2 Application or Register OAuth2 Application to create a new OAuth2 application.

  6. Configure your OAuth2 application settings:

    • Enter a name for the application (e.g., "Nexla Integration")
    • Review and select the permissions or scopes for the application (if applicable)
    • Select 2-legged OAuth or Client Credentials as the grant type

  7. Click Create or Register to create the OAuth2 application.

  8. Your Client ID will be displayed immediately after creation. Copy the Client ID.

  9. Your Client Secret will be displayed immediately after creation. Copy the Client Secret immediately, as it may not be accessible again after you navigate away from the page.

  10. Store both credentials securely, as you will need them to configure your Nexla credential. The Client ID and Client Secret are sensitive information and should be kept confidential.

The Client ID and Client Secret are used to authenticate with the Reltio API authentication endpoint (/oauth/token) to obtain an access token. The access token is then sent in the Authorization header with the Bearer prefix for all subsequent API requests to the Reltio API. The access token is automatically obtained and refreshed by Nexla as needed. If your credentials are compromised, you should immediately revoke them in your Reltio account settings and generate new ones. For detailed information about Reltio OAuth2 authentication, API access, and available endpoints, refer to the Reltio API documentation.

Authenticate​

Credentials required​

FieldRequiredSecretDescription
Client IDYesNoYour Reltio API Client ID.
Client SecretYesYesYour Reltio API Client Secret.

Create a credential in Nexla​

  1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Reltio

ReltioCred.png

  1. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

    Reltio uses OAuth2 2-legged authentication for all API requests. Your Client ID and Client Secret are used to authenticate with the Reltio API authentication endpoint to obtain an access token, which is then used for all subsequent API requests.

  2. Enter your Reltio Client ID in the Client ID field. This is the Client ID you obtained from your Reltio account settings (Settings > API or Developers > OAuth2 Applications). The Client ID is used along with the Client Secret to authenticate with the Reltio API authentication endpoint and obtain an access token.

  3. Enter your Reltio Client Secret in the Client Secret field. This is the Client Secret you obtained from your Reltio account settings. The Client Secret is used along with the Client ID to authenticate with the Reltio API authentication endpoint and obtain an access token. The Client Secret is sensitive information and must be kept confidential.

    Your Reltio OAuth2 credentials can be found in your Reltio account settings under Settings > API or Developers > OAuth2 Applications. The Client ID and Client Secret are used to authenticate with the Reltio API authentication endpoint (/oauth/token) to obtain an access token. The access token is then automatically sent in the Authorization: Bearer {token} header for all subsequent API requests to the Reltio API.

    The access token is automatically obtained and refreshed by Nexla as needed. If your credentials are compromised, you should immediately revoke them in your Reltio account settings and generate new ones. The Client ID and Client Secret provide access to your Reltio account data and should be treated as sensitive information. Keep your credentials secure and do not share them publicly.

    For detailed information about Reltio OAuth2 authentication, API access, and available endpoints, see the Reltio API documentation.

  4. Click the Save button at the bottom of the overlay to save the configured credential. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.

Use as a data source​

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Reltio connector tile, then select the credential that will be used to connect to your Reltio account, and click Next; or, create a new Reltio credential for use in this flow.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Reltio endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Get users for a customer

This endpoint template retrieves all the users belonging to a specific customer from your Reltio account. Only Customer Administrators can use this API. Use this template when you need to retrieve information about users for a specific customer, including user IDs, names, and other user metadata.

  • Enter the customer ID in the Customer ID field. This should be the unique identifier of the customer who has administrator access. The customer ID determines which customer's users will be retrieved.

This endpoint returns all users belonging to a specific customer from your Reltio account, including user IDs, names, and other user metadata. Only Customer Administrators can use this API. The endpoint returns a list of users for the specified customer.

For detailed information about user management, API response structures, and available user data, see the Reltio API documentation.

Get Heavy Operations for a Tenant

This endpoint template gets detailed information about responses with error code 507 for the last one hour for the specified tenant from your Reltio account. Use this template when you need to retrieve information about heavy operations that may have caused quota limit errors.

  • Enter the environment URI in the Environment URI field. This should be the environment URI for your Reltio instance (e.g., https://api.reltio.com). The environment URI determines which Reltio environment will be queried.
  • Enter the tenant ID in the Tenant ID field. This should be the unique identifier of the tenant for which you want to retrieve heavy operations. The tenant ID determines which tenant's heavy operations will be retrieved.

This endpoint returns detailed information about responses with error code 507 for the last one hour for the specified tenant from your Reltio account, including operation details and error information. The endpoint returns a list of heavy operations that may have caused quota limit errors.

For detailed information about heavy operations, API response structures, and available operation data, see the Reltio API documentation.

Filter entities

This endpoint template filters entities by query parameter from your Reltio account. Use this template when you need to retrieve entities that match specific filter criteria, including entity IDs, attributes, and other entity metadata.

  • Enter the environment URI in the Environment URI field. This should be the environment URI for your Reltio instance (e.g., https://api.reltio.com). The environment URI determines which Reltio environment will be queried.
  • Enter the tenant ID in the Tenant ID field. This should be the unique identifier of the tenant for which you want to filter entities. The tenant ID determines which tenant's entities will be filtered.
  • Enter the filter query in the Filter Query field. This should be the filter query parameter that defines the criteria for filtering entities. The filter query determines which entities will be returned based on the specified criteria.

This endpoint returns entities that match the specified filter criteria from your Reltio account, including entity IDs, attributes, and other entity metadata. The endpoint uses the filter query parameter to determine which entities will be returned.

For detailed information about entity filtering, API response structures, filter query syntax, and available entity data, see the Reltio API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right. If the sample data is not as expected, review the selected endpoint and associated settings, make any necessary adjustments, and test again to ensure that the correct information is displayed before saving.

Manual configuration​

Reltio data sources can also be manually configured to ingest data from any valid Reltio API endpoint, including endpoints not covered by the pre-built templates or requiring chained API calls or custom query parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, and path to data.

Reltio API typically uses the GET method for retrieving data. Construct the API URL from your Reltio environment URI (e.g., https://api.reltio.com), tenant ID, and the API path, for example /reltio/api/{tenant_id}/entities or /reltio/api/{tenant_id}/monitoring/heavyOperations. Set the Response Data Path to $[*] to extract all items from a response array, or $ to extract the entire response for single-record endpoints, depending on the endpoint.

Once all of the relevant settings have been configured, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the data source configuration for later use. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination​

Click the + icon on the Nexset that will be sent to the Reltio destination, and select the Send to Destination option from the menu. Select the Reltio connector from the list of available destination connectors, then select the credential that will be used to connect to your Reltio account, and click Next; or, create a new Reltio credential for use in this flow.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Reltio endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Create attributes for an entity

This endpoint template adds attribute values to a specific attribute collection for an entity in your Reltio account using records from a Nexset. The attribute name is defined in the request URL. Use this template when you need to create or update attributes for entities in your Reltio account.

  • Enter the environment URI in the Environment URI field. This should be the environment URI for your Reltio instance (e.g., https://api.reltio.com). The environment URI determines which Reltio environment will receive the data.
  • Enter the tenant ID in the Tenant ID field. This should be the unique identifier of the tenant for which you want to create attributes. The tenant ID determines which tenant's entities will be updated.
  • Enter the entity ID in the Entity ID field. This should be the unique identifier of the entity for which you want to create attributes. The entity ID determines which entity's attributes will be created.
  • Enter the attribute name in the Attribute Name field. This should be the name of the attribute collection where you want to add attribute values. The attribute name is defined in the request URL and determines which attribute collection will receive the values.

This endpoint sends data as JSON in the request body to create attributes for an entity in your Reltio account. Each record from your Nexset will be sent as a separate API request to add attribute values to the specified attribute collection for the entity. The request body should contain the attribute data in the format required by the Reltio API.

The attribute structure must match the Reltio API's expected format for the specified attribute name. For detailed information about attribute creation, request body formats, available attribute properties, and entity management, see the Reltio API documentation.

Manual configuration​

Reltio destinations can also be manually configured to send data to any valid Reltio API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, and request body. Using manual configuration, you can also configure Nexla to automatically send the response received from the Reltio API after each call to a new Nexla webhook data source.

Reltio API typically uses the POST method to create or update attributes and resources, in JSON format. Construct the API URL from your Reltio environment URI, tenant ID, and the API path, for example /reltio/api/{tenant_id}/entities/{entity_id}/attributes/{attribute_name}. The request body must be valid JSON matching the Reltio API's expected structure for the endpoint in use — use {message.json} to send the entire Nexset record as JSON, or construct a custom structure with specific field mappings.

Save & activate​

Once all of the relevant steps in the above sections have been completed, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the destination configuration for later use. To send the data to the configured Reltio endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Reltio endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.