List a Realm's resource approvals
const url = 'http://localhost:11044/api/v1/realms/example/resource-approvals';const options = {method: 'GET', headers: {'X-Embabel-Api-Key': '<X-Embabel-Api-Key>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url http://localhost:11044/api/v1/realms/example/resource-approvals \ --header 'X-Embabel-Api-Key: <X-Embabel-Api-Key>'The graph read and each declared view alias, and whether each is approved.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Name of the captured realm installed in the signed-in owner’s world; non-blank, at most 256 UTF-8 bytes, no control characters and not all * (400 otherwise). 404 when it has no live installation
Responses
Section titled “Responses”OK
A captured realm’s resource approvals: the graph read and each view alias it declares. Answered by listing them and by each grant or revoke
object
The digest of the realm content this installation admitted, 64 lowercase hex characters
The live installation’s id, a UUID. A grant or revoke names it back
Every resource the installation could be granted, the graph read first and then each declared view alias
One thing a captured realm may be granted to read, and whether the owner has granted it
object
Whether the installation holds this grant now
The sentence the owner is shown for this resource, saying what granting it lets the realm read
The resource’s name, as the grant and revoke paths take it: “cypher_query” for the graph read, or “view:” followed by a declared alias for a named view
The installation’s admission revision after this read or change. A grant or revoke names it back as expectedRevision, and is refused if the installation has moved on

