Role Endpoints
This document explains the methods you may use to work with the Role endpoints in the Federated Authority Document database.
Getting Role
Quick-start Knowledge
The full JSON-LD Role object is defined at https://grcschema.org/Role.
Getting a list of Role objects from the Federated Authority Document Database is accomplished by querying the https://grcschema.p.rapidapi.com/Role endpoint using a REST GET. Optional parameters may be provided to filter and paginate the result.
Role List GET
Getting a list of Role object from the Federated Authority Document Database is accomplished by querying the https://grcschema.p.rapidapi.com/Role endpoint using a REST GET with no optional parameters.
Provides a list of all Role objects as Universal Stubs.
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, andoffset
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 fromoffset
= 2. Page 3 fromoffset
= 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.
Role List GET (filtered)
Getting a filtered list of Role objects from the Federated Authority Document Database is accomplished by querying the https://grcschema.p.rapidapi.com/Role/ 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.
Role GET (by ID)
Getting a single Role object from the Federated Authority Document Database is accomplished by querying the https://grcschema.p.rapidapi.com/Role/:id endpoint using a REST GET.
Last updated