Overview#
Update the data and metadata associated with an existing data token. This allows you to replace the stored data or modify token metadata without creating a new token.Update Data Token#
Endpoint: POST /data-token/update-dataContent-Type: application/jsonRequest Parameters#
| Parameter | Type | Required | Description |
|---|
dataToken | string | Yes | The token identifier to update |
data | string | Yes | New encrypted data to replace existing data |
meta | object | No | Metadata object containing configuration |
meta.information_security_risk | object | No | Security classification metadata |
meta.file | object | No | File metadata |
meta.data | object | No | Data type metadata |
Use Case#
Use this endpoint when you need to update data associated with an existing token or modify its metadata. This is useful for:Replacing outdated data while maintaining the same token identifier
Updating metadata as security classifications or file attributes change
Correcting metadata without re-exchanging data
Maintaining stable token references across data updates
The new data follows the same encryption and routing process as initial exchange: encrypted by Privicore and distributed to registered devices.The token must be a permanent token (data already exchanged)
New data should be encrypted by the application before update
Metadata updates are optional - omit fields to leave them unchanged
Update operations replace existing data and metadata entirely