home

Applications

ReltioProductsDeveloper resourcesRolesApplicationsObjectives
ReltioProductsDeveloper resourcesRolesApplicationsObjectives

Unify and manage your data

Show Contents

thumbnailApplications

Configure Zero Copy Data integration with Snowflake using APIs

Restore a deleted Interaction mapping for Zero Copy Integration

Learn how interaction mappings behave after deletion and how to restore them in Zero Copy Integration for Snowflake.

When working with Zero Copy Integration, you define interaction mappings to connect external Snowflake tables to Reltio interaction types. These mappings can be created, deleted, and reused. When mappings are deleted they are not fully removed, and attempting to create a new interaction mapping with a deleted mapping payload may produce unexpected results. Understanding the mapping lifecycle helps you avoid conflicts and ensure mappings work as expected.

Mapping lifecycle and soft-delete behavior

Interaction mappings follow a soft-delete lifecycle. When you delete a mapping using the DELETE /zero-copy-interactions/mappings/{mappingId} endpoint, it is marked as deleted internally but is not permanently removed. As a result:
  • Using GET /zero-copy-interactions/mappings/{mappingId} returns no result for the deleted mapping.
  • Using POST /zero-copy-interactions/mappings/{mappingId} to create a new mapping with the same definition returns "successful": true, but the returned mapping object includes "deleted": true.
  • Even though the mapping appears deleted, its definition still exists in a soft-deleted state and blocks the creation of a new mapping with the same definition.
This behavior is different from a traditional delete-and-recreate flow. You cannot simply recreate a mapping using the same payload after deletion unless you use the restore process.

Restoring a deleted mapping

To reuse a previously deleted interaction mapping, you must restore it using the dedicated restore API endpoint: 


PUT /reltio/api/tenants/{tenantId}/zero-copy-interactions/mappings/{mappingId}/restore
This call reactivates the original mapping, setting "deleted": false in the system. Once restored:
  • The mapping can be used as if it were newly created.
  • It appears again in GET calls.
  • You can update or delete it as needed.
Always use the restore API if you need to reuse the same mapping definition after deletion. Attempting to re-create the mapping with the same payload will result in a soft-deleted object and may lead to inconsistencies.

Updated on February 20, 2026

Footer

You've found your way to a temporary environment. Content is not complete or final. Looking for Reltio documentation? Go to docs.reltio.com.

© 2026 The RELTIO® mark is a registered trademark of Reltio, Inc. in the United States and other countries; DataDriven and Reltio Data Cloud are trademarks of Reltio, Inc. Other names or marks are trademarks of their respective owners.

Terms and Conditions, Privacy Policy, and