Mapping the organizational structure in filters, recommendations and CUE is made available by uploading the file via API. Your enrichment tags are stored as a single csv file. To update the CSV file using the API, you need to:

GET the current configuration file
In a text editor - Update the entries as needed
POST the updated file to replace the existing configuration in your account

📘
Linked Account values in the CSV file
Each row in the file contains a linked account and the taggings for that account
The upload process then:

Validates the value of the linked account of each row

If the linked account value exists in one of the accounts - the row is imported

If the linked account value does not exist in any of the payer accounts or the organization - the row is filtered out

In the case that all linked accounts do not exist - you will get a 200 OK response, while the actual content of the enrichment tags object will be empty

✅
Note about UM 2.0 usage of the enrichment tags API
The API key is built of (user key):(account key):(division)
The API key for the enrichment tags upload should be constructed in the following manner:
user key - standard user key, with the following permissions:

Data access permissions to accounts references by the API request

Action Permissions "Cost-Allocation -> Create"

account key - should contain the payer/billing account id
division - Should be empty