GET /dataChanges

Returns collection of data changes accessible by a user. User can pass offset and limit query params to get the list of data changes. The type of responses is based on "type" query parameter. The user gets a default response containing: id, name, displayName.

The user can also receive "summary" or "full" response based on the value set for the "type" parameter.

Secured by

Servers

Query parameters

Name Type Required Description
limit Integer No

The maximum number of object data entries to be included in the response.

  • default: 20
  • max: 500
name String No

The name of a data change.

Note: Either "type" or "name" query parameter must be set in order to receive the response as object "dataChangeResponseList" below.

  • default: -- (empty)
type String Yes

How much data change information to be returned. Note: The model response for HTTP 200 below is for type "summary"

Note: Either "type" or "name" query parameter needs to be set in order to receive the HTTP 200 response below.

  • default: -- (empty)
  • full: Every element in type "summary", plus description, application, categories, tags, mappings
  • summary: Returns summarized data change details specified in the model "dataChangeSummary"

Valid values:

  • "full"
  • "summary"
offset Integer No

The offset to the first object in a collection to include in the response. default: 0

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.