Unify and manage your data

Show Page Sections

Search Data Change Requests

Learn more about the Search api to search for data change requests.

Use the get data change request (DCR) API operation to search for DCRs by users and/or URIs of the affected objects. The search filter must contain at least one equals or in condition for createdBy or objectURI properties. Otherwise, the operation returns the CHANGE_REQUEST_SEARCH_FILTER_INCORRECT error.
Note: The search and filtering actions are supported only for createdBy and objectURI parameters (URIs of affected objects in the Data Change Request). The operation only returns DCRs which are allowed to be viewed by the user invoking the request.

Request:

GET {TenantURL}/changeRequests
Table 1. Parameters

Parameter

Name

Required

Details

Headers Authorization Yes Information about authentication access token in format "Bearer <accessToken>" (see details in Auth API).
Query filter Yes

Enables data change request filtering by a condition. Format for filter query parameter:

filter=({Condition Type}[AND/OR {Condition Type}]*)

Only the following conditions are supported:

  • equals(property, 'value') - exact match condition

  • in(property,'value1,value2,...') - returns data change requests which have property value contained in the specified values list

Search by the following properties is supported:

  • createdBy

  • objectURI

Note:
  • Search is case sensitive.
  • Empty filter is not allowed.
max No

Positive Integer value to identify the maximum number of data change requests to return in a response. Can be used to organize pagination in combination with the offset parameter.

Default value is 10 .

offset No

Positive Integer value to identify the starting element in a result set to be returned in a response. Can be used to organize pagination in combination with the max parameter.

Default value is 0.

Response

JSON array of the data change request objects from a tenant matching the filter request.

Example of a search request

GET {tenantUrl}/changeRequests?filter=in(createdBy,'User') and in (objectURI,'entities/00005KL')&offset=0&max=5

Response

[{ "URI": "changeRequests/0000OVV", "createdBy": "User", "createdTime": 1445452647170, "updatedBy": "User", "updatedTime": 1445452647170, "changes": { "entities/00005KL": [{ "id": "0000jon", "type": "INSERT_ATTRIBUTE", "createdTime": 1445452647560, "createdBy": "User", "attributePath": "ProductMetrics/3/ExternalID", "newValue": { "value": "NewId" }, "crosswalk": { "type": "configuration/sources/Veeva", "value": "e1" } } ] } } ]
Note: The search request is limited to fetching a maximum of 100,000 change requests to prevent platform overload on larger queries.