Unreleased documentation. These pages follow the main branch and can change before the next release. For supported guidance, use v0.44.0.
List every grant on one document, in any state; only the custodian may.
const url = 'https://example.com/v1/documents/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/grants?limit=50';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://example.com/v1/documents/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/grants?limit=50' \ --header 'Authorization: Bearer <token>'Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Query Parameters
Section titled “Query Parameters”The opaque cursor a previous page returned as nextCursor.
Items per page.
Responses
Section titled “Responses”The operation succeeded.
One page of document grants, oldest first.
object
One document grant.
object
The recipient a grant names: a subject at the configured token issuer, and the actor kind a caller must resolve to for the grant to release anything to it.
object
An actor kind: a service, or a human person.
An identifier another system issues, written exactly as its issuer gives it.
Where a grant stands.
The cursor of the next page; absent on the last page.
Example
{ "items": [ { "grantee": { "kind": "service" }, "state": "active" } ]}A problem: request.invalid.
object
Example
{ "code": "request.invalid", "type": "https://id.registrystack.org/problems/registry-documents/authentication/refused"}A problem: authentication.refused.
object
Example
{ "code": "authentication.refused", "type": "https://id.registrystack.org/problems/registry-documents/authentication/refused"}Headers
Section titled “Headers”The bearer challenge.
A problem: profile.not-authorized.
object
Example
{ "code": "profile.not-authorized", "type": "https://id.registrystack.org/problems/registry-documents/authentication/refused"}A problem: resource.not-found.
object
Example
{ "code": "resource.not-found", "type": "https://id.registrystack.org/problems/registry-documents/authentication/refused"}A problem: request.method-not-allowed.
object
Example
{ "code": "request.method-not-allowed", "type": "https://id.registrystack.org/problems/registry-documents/authentication/refused"}A problem: service.unavailable.
object
Example
{ "code": "service.unavailable", "type": "https://id.registrystack.org/problems/registry-documents/authentication/refused"}Headers
Section titled “Headers”Whole seconds to wait before trying again.
Cookies on Registry Stack
We use optional cookies to understand how you use the main Registry Stack website and this documentation. If you contact us, we may link this activity to your enquiry. You can change your choice at any time. Read the privacy policy.
Your browser asks sites not to track you, so optional tracking stays off.
We could not use or save that choice. Optional tracking remains off.