How pagination works

This endpoint returns results in pages. Use the following query parameters to navigate through them:

The response envelope contains the following fields:

To retrieve all processing activities, iterate through pages until you have collected total records.

Example: to retrieve the second page with 50 records per page:

GET /v1/ws/{workspaceId}/DataProcessings?page=2&size=50

💡

Tip: To retrieve everything in one shot, set size to 100 (the maximum) and iterate until page * size >= total.

Selecting additional fields in the response

By default, the paginated endpoint only returns core fields for each processing activity.
Related objects are excluded to reduce payload size and improve performance.

To include them, use the select query parameter. Important: the select parameter is exclusive — as soon as you use it, only the explicitly listed relations are loaded. If you omit a value (e.g. Tags), it will be empty in the response, even if data exists.

Always pass the full set of relations you need. The available values are:

To combine multiple values, pass them as a comma-separated list in a single select parameter:

GET /v1/ws/{workspaceId}/DataProcessings
  ?select=Actors,Actors.Actor,Area,Tags,Tags.Tag,WorkflowStep,Owners,Owners.User,Assets,DataRetentionRules,Purposes,SecurityMeasures,PersonCategories,Attachments

⚠️

Performance note: Selecting many related objects — especially on large workspaces — increases response time and payload size. Only request what your use case requires.