Profile reprocessing API

Identity resolution is only available on Business tier plans. You can use it with or without Customer Studio.

Overview

The profile reprocessing API allows you to programmatically delete and re-ingest identity records for specific profiles. This enables you to handle GDPR deletion requests and correct misidentified profiles by triggering selective reprocessing of your identity graph.

Use cases

GDPR compliance: Process data deletion requests by removing specific identifiers from your identity graph.
Supercluster resolution: Reprocess profiles after identifying and blocklisting problematic identifiers that caused incorrect merging.

How it works

When you queue profiles for reprocessing, Hightouch:

Finds all profiles (ht_ids) containing the specified identifiers.
Deletes all records associated with those profiles from the identity graph.
Blocks the given identifiers to prevent them from being re-ingested during future IDR runs. This is the default behavior (block: true).

If you're reprocessing to fix a supercluster rather than to delete data, you can set block: false in your API request. This resets the graph state without permanently blocklisting the identifier, so it can be re-ingested correctly on the next run.

Re-ingests remaining data from your source tables during the next IDR run.

When an ht_id is reprocessed, the original ht_id is permanently deleted. Depending on how the remaining records resolve, this may result in no new ht_ids (if records merge into other existing profiles), one new ht_id, or multiple new ht_ids. The original ht_id value will never be reused, assuming there are no full re-runs of your identity graph.

Important: Delete the relevant data from your source tables before calling this API. If the data still exists in your warehouse, it will be re-ingested during the next IDR run.

API reference

You can manage profile reprocessing programmatically using the following API endpoints:

These endpoints allow you to:

Queue identifiers for reprocessing or deletion.
Check the status of ongoing or completed jobs.
Integrate reprocessing logic into your GDPR or identity maintenance pipelines.

For full request and response schemas, authentication requirements, and example code snippets, visit the Hightouch API Reference.

Workflow

Delete source data — Remove relevant identifiers from your data warehouse tables that feed into IDR.
Queue for reprocessing — Submit a POST request to /idr/{graphId}/queue-for-reprocessing with the identifiers you want to remove.
Track the request — The API immediately returns a requestId for asynchronous processing. Check status with GET /idr/{graphId}/reprocess-status/{requestId}.
Automatic reprocessing — During the next scheduled IDR run after the job completes, Hightouch deletes and re-ingests the affected profiles.

Processing timeline

The queuing and marking of identifiers happen asynchronously after you call the API.
Actual deletion and re-ingestion occur during the next IDR run after the job finishes.
Expect one full IDR run cycle to see changes reflected in your resolved identity tables.

Limitations

Batch size: For large reprocessing requests, split identifiers into multiple batches to avoid timeouts or processing delays.