Skip to main content

Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that sends data to a Reltio location.
reltio_api.png

Reltio

Create a Reltio Destination​

  1. Click the + icon on the Nexset that will be sent to the Reltio destination, and select the Send to Destination option from the menu.

  2. 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.

  3. In Nexla, Reltio destinations can be created using pre-built endpoint templates, which expedite destination setup for common Reltio endpoints. Each template is designed specifically for the corresponding Reltio endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    Reltio destinations can also be configured manually, allowing you to send data to Reltio endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Reltio endpoints. Each template is designed specifically for the corresponding Reltio endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, 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.

Configure Manually​

Reltio destinations can be manually configured to send data to any valid Reltio API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

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.

API Method​

  1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Reltio API from the Method pulldown menu. Reltio API typically uses POST method for creating resources and attributes.

Data Format​

  1. Select the format in which the Nexset data will be sent to the Reltio API from the Content Format pulldown menu. Reltio API expects JSON format for all requests.

API Endpoint URL​

  1. Enter the URL of the Reltio API endpoint to which data will be sent in the URL field. This should be the complete URL including your environment URI, tenant ID, the API path (e.g., /reltio/api/{tenant_id}/entities/{entity_id}/attributes/{attribute_name}), and any required query parameters. Include any required path parameters in the URL.

Ensure the API endpoint URL is correct and accessible with your current credentials. The Reltio API endpoint URL should point to the endpoint where you want to create attributes or resources. The endpoint URL should include your environment URI, tenant ID, and the appropriate API path. You can test the endpoint using the Test button after configuring the URL.

Request Body​

  1. Configure the request body that will be sent to the Reltio API. The request body should contain the resource data formatted as JSON, with field names matching the Reltio API's expected structure. The request body format is typically {message.json} to send the entire Nexset data as JSON, or you can construct a custom JSON structure with specific field mappings.

The request body must be valid JSON and must match the Reltio API's expected format for the specific endpoint you're using. Reltio API uses specific structures for different endpoints (attributes, entities, etc.). For detailed information about request body formats, available endpoints, and resource structures, see the Reltio API documentation.

Save the Destination​

  1. 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.