ListEntitlements
/api/v1/entitlementsList or search for the underlying set of access that a user, group, or team has to a Resource.
Resources are low-level APIs that represent external objects, and users
should be shown Listings and ListingRoles instead. Use
ListListingRoleEffectiveSubjects to determine what a user or team has
access to.
Example request
Section titled “Example request”curl \ -H "Authorization: Bearer ${OBLIQUE_API_KEY}" \ "https://us.oblique.security/api/v1/entitlements"Set OBLIQUE_API_KEY to your API key.
curl \ -H "Authorization: Bearer ${OBLIQUE_API_KEY}" \ "https://eu.oblique.security/api/v1/entitlements"Set OBLIQUE_API_KEY to your API key.
Query parameters
Section titled “Query parameters”pageSizeinteger (int32)The maximum number of entitlements to return. This service may return fewer than this value.
pageTokenstringA page token, received from a previous
ListEntitlementscall.filterstringEntitlements may be filtered by the subject they apply to, the resource or resources they grant access to, or the integration that reports those resources. More advanced filters are rejected.
Examples:
subject="teams/{team}"subject="users/{user}"orsubject="users/me"subject="integrations/{integration}/accounts/{account}"subject="resources/{resource}"resource="resources/{resource}"resource="resources/{resource},resources/{resource}"integration="integrations/{integration}"
A resource can appear on either side, and the two are opposites. Filtering by subject returns the entitlements nesting that resource inside others; filtering by resource returns the entitlements granting access to it. The resource filter accepts a comma-separated list of resources; filtering by integration returns the entitlements granting access to any resource that integration reports.
showDeletedbooleanIf true, the response will include entitlements in resources that have been deleted.
Response
Section titled “Response”200ListEntitlementsResponseentitlementsEntitlement[]namestringAssigned by Oblique. Name of the entitlement of the format
entitlements/{entitlement}.resourcestringrequiredSet once, when the resource is created. The resource that this entitlement grants access to.
Format:
resources/{resource}subjectstringrequiredSet once, when the resource is created. The subject that is granted access to the resource. This can be a user, team, group, an account in an integration, or another resource.
An account subject grants the access to that account rather than to the directory user behind it. The account must belong to the same integration as the resource.
A resource subject represents a nested membership in the system that owns both resources, such as a Google group that is a member of another Google group. Both resources must come from the same integration, and the system must support that pairing: a Google group nests in a Google group, an Okta group in an Okta app, and a GitHub team in a GitHub team. A resource can’t be a member of itself.
Format:
users/{user},teams/{team},groups/{group},integrations/{integration}/accounts/{account},resources/{resource}rolesRole[]The roles the subject holds on the resource. A resource can grant a subject more than one role at once, such as a Cloudflare policy that carries several permission groups.
A subject holding the system’s default role has that role recorded explicitly, so an empty list means the roles are unknown rather than that the subject holds none.
displayNamestringrequiredThe role’s name as the system that owns the resource names it. For example, a Google group membership is
MEMBER,MANAGER, orOWNER, and a Cloudflare permission group has a name such as “OAuth App Registrations Read”.Every system names its roles differently, so values are recorded verbatim and are not validated.
idstringrequiredThe identifier the system that owns the resource uses for this role. Opaque to Oblique, and the same as
display_namefor a system that names a role only one way.
One of
expireTimestring (date-time)If present, when this access expires. This field is always provided on output.
ttlstring (duration)Input only. The TTL for the entitlement.
createTimestring (date-time)read-onlyCreate and update timestamps.
updateTimestring (date-time)read-onlyjustificationstringHuman readable justification for the entitlement to be granted. For example, this may contain a link to a ticket or other artifacts.
importedbooleanSet once, when the resource is created. When true, this boolean indicates this entitlement was “imported” from a syncing process, such as reading data from Okta or Google Groups. User created entitlements will always cause this field to be false or unset.
requeststringread-onlyIf present, the request that most recently created or updated this entitlement.
Format:
requests/{request}actionUpdateTimestring (date-time)read-onlyWhen this entitlement was created, or the last time its roles changed.
If this entitlement is the result of a change in Oblique, it may not have been actuated to a remote system yet. See
sync_action_update_time.syncActionUpdateTimestring (date-time)read-onlyThe
action_update_timewhen this entitlement was last observed to be in-sync with the remote system.For imported entitlements, this will always match
action_update_time, since Oblique observes the remote state at the same time it creates the entitlement.For entitlements written to external systems, this is the
action_update_timefor the entitlement that was acted on.sync_action_update_timeis either older thanaction_update_time, indicating an entitlement hasn’t been pushed yet. Or equivalent toaction_update_timewhen an entitlement has been reconciled.
nextPageTokenstringA token, which can be sent as
page_tokento retrieve the next page.totalSizeinteger (int32)The total number of entitlements that match the request.
Errors
Section titled “Errors”| Status | Meaning |
|---|---|
400 | Malformed request |
401 | Missing or invalid API key |
403 | Not allowed for this API key |
404 | Not found |
429 | Too many requests |
500 | Internal server error |