getMyAccess
const url = 'https://example.com/api/v1/me/access';const options = {method: 'GET'};
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/api/v1/me/accessThe signed-in account’s role, effective capabilities, and Media content access. Available to every enrolled account with the read scope.
Responses
Section titled “ Responses ”Effective access
object
object
object
Role key. The built-in roles are owner, administrator, editor, contributor, and viewer. Custom role keys start with “custom.”. Decide authorization from the capabilities the server reports, not from the role key.
object
Folders the account may upload into. Absent when the account reaches the whole library, which may also use the root.
The signed-in account’s screen access. An account without a stored policy reads as restricted with no grants.
object
All reaches every screen. restricted reaches the union of the granted locations and Display Groups, and nothing without grants.
Locations granted directly. Empty for all screens.
Display Groups granted directly. Empty for all screens.
Example
{ "data": { "role": { "key": "owner" }, "content": { "libraryMode": "all", "tagMode": "all" }, "screens": { "mode": "all" } }}Dashboard authentication required