Enrichment

Unassign Config From List

Stop showing a column on one list. Free.

The values stay in the database - this hides the column, it does not delete enrichment you paid for. Re-assigning brings them back.

BOTH gates are declared: the config's home list and the list being detached. They are different lists and a caller can easily have access to one and not the other.

delete/enrichment/configs/{config_id}/assignments/{list_id}

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/enrichment/configs/{config_id}/assignments/{list_id}
  • Auth: HTTP bearer

Path parameters

config_idstring uuid required
list_idinteger required

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Response

Successful Response

dataEnrichmentPayload required

One enrichment object, open-shaped.

Open on purpose: a workbench column set is defined by the CUSTOMER at runtime, and the enrichment result shapes grow with every provider added. Pinning them would drop whatever a provider returned that this contract had not caught up on, which on an enrichment surface is the data the customer paid for.

Changes

No recorded changes to this operation across all 2 revisions of this API.