Reltio Delete (By URI)

Snap used to delete Reltio objects by URI.

Table 1. Reltio Delete (By URI)
Field Name Description
Snap Type: Write

This Snap is used to delete the Reltio Objects (Entities/ Relations/ Categories) from the mentioned Tenant based on the URI supplied. It also supports the Bulk operation by using Bulk Delete parameter. The Reltio Delete (URI) Snap cannot be used for deleting Interactions since they are transaction based data and cannot be deleted.

ETL Transformations and Data Flow

The Reltio Delete (URI) Snap extract's (or deletes) the corresponding data from the Reltio tenant.

Input & Output

  • Input: Input view is optional and is required only to pass the URI from upstream snap or value in that field.
  • Output: Response for the snap contains either success or error based on the URI deleted or not.


  • Ultra pipelines: May work in Ultra Pipelines.
  • Spark (Deprecated) mode: Not supported in Spark mode.
Prerequisites: Reltio account with a valid Tenant ID so that Tenant URL can be formed/API for Account Settings. Also, the Reltio account must have sufficient access in order to be able to delete Objects in the Tenant.
Limitations and Known Issues None at the moment.
Configurations: Account & Access

This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. See Reltio Account for information on setting up this type of account.


This Snap has exactly one document input view.
This Snap has exactly one document output view.
This Snap has at most one document error view and produces zero or more documents in the view.
Troubleshooting: None at the moment.


The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline.

Tenant URL


This determines the Reltio host with Tenant ID. The format to be used is https://<reltio_host>/api/tenant_id>.


Default value: https://<your_reltio_host>/reltio/api/<tenant_id>

This value can be provided dynamically as a pipeline parameter or directly in the Snap, but not as an upstream parameter.



This describes the actual Object which needs to be deleted based on the URI parameter. For example: “uri”: “entities/abcd1234” is a part of Reltio object (Entity here).

Also if the Bulk delete property is enabled, then multiple entities' URIs can be provided separated by commas.

Default value: [None]

Bulk delete

This property enables deleting multiple Entities at a time; accepts a comma-separated list of URLs.

Default value: Not selected

Retry limit

The maximum number of times the Snap will attempt to get the response. Since Reltio uses the exponential back off retry policy only for HTTP Status Codes 502, 503 and 504 and no retry policy for HTTP Status Codes 401, 403, 404, 500.

Default value: 5

Maximum value: 10

This value can be provided dynamically as a pipeline parameter or directly in the Snap but not as an upstream parameter.

Execute during preview

Executes the Snap during a pipeline Save operation so that the output view can produce the preview data.

Default value: Not selected

See the below examples for the basic and advanced use case and typical Snap configurations for the Delete (By URI) operation.