How Can We Help?
Using Web Service to See ChangesUsing Web Service to See Changes
What
You want to view changes in Pure via the 524/changes/ endpoint on the webservice and specifically see where there have been updates, deletions, etc. or see this information by type of change or newest changes. How might this be possible?
How
- The changes endpoint, in principle, reads audit logs in Pure.
- You can obtain “changes” such as 'created' through the changeType field as pictured below. However, the webservice does not support filtering on these change types (E.g. filter by UPDATE, DELETE, etc.).
<changeType>CREATE</changeType>
- The first call to the changes endpoint is “changes” since the start date; any subsequent calls should use the resumption token to avoid getting duplicate information back. The resumption token is used to return all the changes after the last call. For example,
<result xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://localhost:8080/ws/api/518/xsd/schema1.xsd"> <count>12</count> <navigationLinks> <navigationLink ref="next" href="http://localhost:8080/ws/api/518/changes/eyJzZXF1ZW5jZU51bWJlciI6Mzc5MjU0NX0="/> </navigationLinks> <resumptionToken>eyJzZXF1ZW5jZU51bWJlciI6Mzc5MjU0NX0=</resumptionToken> <- use this token in next call <moreChanges>false</moreChanges> <items> </items> </result>
- One page in response to the call will contain up to 100 changes depending on whether or not the audits read are allowed to be exposed in the webservice. As long as you get the <moreChanges>true<moreChanges> on the call, you may continue to read the next page by using the resumption token. Once you have read all the pages, you will have all “changes” that have been done in Pure since the starting date.
More information
- More details on Changes Endpoint can be found on Harvesting content from the Pure web services (changes)
Updated at October 10, 2024