Anonymization API - PUT anonymization job

• Reference
• Updated on Nov 03, 2026

Creates a user session anonymization job. The job anonymizes all user sessions in the specified timeframe by masking the user ID (userIds) and IP address (ips).

To identify user sessions to be anonymized, you can specify either the user ID, IP address, an internal application ID or a combination of them. If you specify multiple criteria, OR logic applies.

Regardless of how you identify user sessions, both the user ID and IP address are masked. You can't undo anonymization.

The request produces an application/json payload. The response body contains the clusterRequestIds in case of Premium High-Availability clusters and the requestId of the anonymization job, which you can use to check the job status.

Parameters

Response

{
  "clusterRequestIds": [
    {
      "dcName": "string",
      "id": 1
    }
  ],
  "requestId": "-4013759873546847071|7354684707140137598"
}

Best practices

Combine all user IDs and IP addresses into a single request

Anonymization jobs are processed one after another, and each job processes all user sessions in the specified timeframe. A job can therefore take a long time, and every additional request delays the jobs that are enqueued after it.

If you need to anonymize several users, submit one request that contains all of their user IDs and IP addresses instead of one request per user ID or IP address. Repeat the userIds and ips query parameters for each value:

PUT /api/v1/anonymize/anonymizationJobs?userIds=john.smith&userIds=mary.smith&ips=192.0.2.15&ips=198.51.100.7

If your list is too long for a single request URL, split it into a few large requests rather than many small ones.

Specify timestamps in UTC milliseconds

The startTimestamp and endTimestamp parameters accept Unix epoch timestamps in milliseconds, in UTC. Common mistakes:

To convert a UTC date to a timestamp in milliseconds, you can use, for example:

# Linux (GNU date)
date -u -d '2018-09-01T00:00:00Z' +%s000
# macOS (BSD date)
date -u -j -f '%Y-%m-%dT%H:%M:%S' '2018-09-01T00:00:00' +%s000

If you're not sure in which timeframe the user sessions occurred, omit startTimestamp. The job then covers all stored user session data up to endTimestamp (or the current time, if endTimestamp isn't set).

Check the job status before you submit the request again

A job that is waiting for execution reports progress of -1. This is expected when other jobs are queued before it. Don't submit the same request again; use the returned requestId to check the job status instead.

Validation errors

The request is rejected with response code 400 if:

Example

In this example, the request starts a job to anonymize all sessions of users john.smith and mary.smith in the time frame between 00:00:00 September 1, 2018 and 23:59:59 September 10, 2018 UTC (corresponding to the 1535760000000 and 1536623999000 timestamps, respectively).

The API token is passed in the Authorization header.

The response contains the ID of the anonymization job, which can be used to check its status.

Curl

curl -X PUT \
  'https://mySampleEnv.live.dynatrace.com/api/v1/anonymize/anonymizationJobs?startTimestamp=1535760000000&endTimestamp=1536623999000&userIds=john.smith&userIds=mary.smith' \
  -H 'Authorization: Api-Token dt0c01.abc123.abcdefjhij1234567890'

Request URL

https://mySampleEnv.live.dynatrace.com/api/v1/anonymize/anonymizationJobs?startTimestamp=1535760000000&endTimestamp=1536623999000&userIds=john.smith&userIds=mary.smith

Response content

{
  "clusterRequestIds": [
    {
      "id": -7520440752290577000,
      "dcName": ""
    }
  ],
  "requestId": "-7520440752290577781"
}

Response code

200