This document explains the methods you may use to work with the ChangeHistory endpoints in the Federated Authority Document database.
Getting ChangeHistory
Quick-start Knowledge
The full JSON-LD ChangeHistory object is defined at https://grcschema.org/ChangeHistory.
Getting a list of AuditData objects from the Federated Authority Document Database is accomplished by querying the https://grcschema.p.rapidapi.com/ChangeHistory endpoint using a REST GET. Optional parameters may be provided to filter and paginate the result.
ChangeHistory List GET
Getting a list of ChangeHistory object from the Federated Authority Document Database is accomplished by querying the https://grcschema.p.rapidapi.com/ChangeHistory endpoint using a REST GET with no optional parameters.
Provides a list of all ChangeHistory objects.
Pagination is provided for the list where count is the total quantity of objects in the data-set, limit is how many objects are returned in the current list, and offset is the first object in the set from that offset point. This is configurable in the request, but the default is a limit of 50 objects starting from offset 0.
In the below example, with a limit of 2, page 1 starts from offset 0 with two values (limit). Page 2 starts from offset= 2. Page 3 from offset= 4, etc. There would be 5 pages to display the data - two objects at a time. This is illustrative only, and the actual local pages will depend on your limit and count.
Getting a filtered list of ChangeHistory objects from the Federated Authority Document Database is accomplished by querying the https://grcschema.p.rapidapi.com/ChangeHistory/ endpoint using a REST GET with url parameters.
These are the parameters you can optionally supply to the filter. These fields work as a logical AND.
Field
Description
object_id
Filters by object_id. (both creation and changes)
person_id
Filters by the person id. (both creation and changes)
organization_id
Filters by the organiation id. (Future Use)
team_id
Filters by the team id. (Future Use)
type
Filters by the type of the modification. (e.g. POST, PATCH)
endpoint
Filters by the API endpoint. (e.g. Person, Organization)
search
Searches across all searchable fields.
sort_dir
0 = descending, 1 = ascending
limit
Combined with offset, provides pagination by limiting results.
offset
Combined with limit, provides pagination by shifting the first record.
ChangeHistory GET (by ID)
Getting a single ChangeHistory object from the Federated Authority Document Database is accomplished by querying the https://grcschema.p.rapidapi.com/ChangeHistory/:id endpoint using a REST GET.