ListUserAttributes
/api/v1/users/{user}/userattributesList attributes for a given user. Attributes sourced from external systems such as Okta, Google, Slack, and Workday, are used to determine membership in attribute-based Groups.
Example request
curl \ -H "Authorization: Bearer ${OBLIQUE_API_KEY}" \ "https://us.oblique.security/api/v1/users/{user}/userattributes"Set OBLIQUE_API_KEY to your API key.
curl \ -H "Authorization: Bearer ${OBLIQUE_API_KEY}" \ "https://eu.oblique.security/api/v1/users/{user}/userattributes"Set OBLIQUE_API_KEY to your API key.
Path parameters
parentstringrequiredFormat:
users/{user},users/-to list across all users, orusers/meto list for the authenticated user.
Query parameters
pageSizeinteger (int32)The maximum number of user attributes to return. This service may return fewer than this value.
pageTokenstringA page token, received from a previous
ListUserAttributescall.filterstringOptional filter to be used. This currently only supports filtering by integration name:
filter=integration="integrations/okta"
Response
200ListUserAttributesResponseuserAttributesUserAttribute[]namestringAssigned by Oblique.
createTimestring (date-time)read-onlyCreate timestamp of the attributes. This is always the same as the parent user.
updateTimestring (date-time)read-onlyThe last time that attributes were modified.
integrationstringrequiredThe integration that manages the attribute.
Format:
integrations/{integration}keystringrequiredThe key of the attribute, such as “department” or “costCenter”.
valuestringrequiredThe value of the attribute, such as “Engineering” or “12345”.
nextPageTokenstring
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 |