The user data is encrypted and does not have blind index searching.
Use the search endpoint to search for personal identifyable information such as first name, last name, full name, employee ID, etc.
Documentation Index
Fetch the complete documentation index at: https://docs.provisionr.io/llms.txt
Use this file to discover all available pages before exploring further.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Available includes are manager-user, manager-user-count, manager-user-exists, workspace-user, workspace-user-count, workspace-user-exists, parent-user, parent-user-count, parent-user-exists, secondary-users, secondary-users-count, secondary-users-exists, direct-report-users, direct-report-users-count, direct-report-users-exists, workspace-integration, workspace-integration-count, workspace-integration-exists, directory-identities, directory-identities-count, directory-identities-exists, policy-conditions, policy-conditions-count, policy-conditions-exists, policy-users, policy-users-count, policy-users-exists, policy-rules-manifest, policy-rules-manifest-count, policy-rules-manifest-exists, policy-rules-qualified, policy-rules-qualified-count, policy-rules-qualified-exists, policy-rules-staged, policy-rules-staged-count, policy-rules-staged-exists, policy-rulesets, policy-rulesets-count, policy-rulesets-exists. You can include multiple options by separating them with a comma.
Filter by an exact ID match.
"drusr_01hq8xyzabc123def456ghi789"
Filter by a partial ID match.
"d662"
Filter by the associated workspace integration ID.
"wsitg_01hq8xyzabc123def456ghi789"
For secondary users, you can filter by the parent user ID.
"drusr_01hq8xyzabc123def456ghi789"
Filter by users that report to a specific manager user ID.
"drusr_01hq8xyzabc123def456ghi789"
Filter by the first (given) name of the user (exact match).
"Dade"
Filter by the first (given) name of the user (partial match).
"Dad"
Filter by the last (family) name of the user (exact match).
"Murphy"
Filter by the last (family) name of the user (partial match).
"Mur"
Filter by the full (first and last) name of the user (exact match).
"Dade Murphy"
Filter by the full (first and last) name of the user (partial match).
"Dade"
Filter by the email address of the user (exact match).
"dmurphy@example.com"
Filter by the email address of the user (partial match). This is useful for searching by email handle or domain name.
"dmurphy"
Filter by the username of the user (exact match).
"dade.murphy"
Filter by the username of the user (partial match).
"z3r0c00l"
Filter by the badge ID number of the user (exact match).
"a1b2c3d4e5"
Filter by the badge ID number of the user (partial match).
"a1b2c"
Filter by the employee ID number of the user (exact match).
"a1b2c3d4e5"
Filter by the employee ID number of the user (partial match).
"a1b2c"
Filter by the alternate employee ID number of the user (exact match).
"a1b2c3d4e5"
Filter by the alternate employee ID number of the user (partial match).
"a1b2c"
Search organization metadata key/value pairs for any partial string. For more granularity and specific keys, use the Policy Users endpoint for a specific Directory Dimension or Attribute.
"Engineer"
Search custom organization business logic metadata key/value pairs for any partial string.
Filter users that are managers (have direct reports) or are not managers (individual contributors).
The state of the Directory User. See the Response Body below for more details on each state type.
"active"
Filter results by date. Any parsable date format can be used.
"2025-01-01 or 2025-01-01 12:30:00 or 2025-01-01T12:30:00Z"
Filter results by date. Any parsable date format can be used.
"2025-01-01 or 2025-01-01 12:30:00 or 2025-01-01T12:30:00Z"
Filter results by date. Any parsable date format can be used.
"2025-01-01 or 2025-01-01 12:30:00 or 2025-01-01T12:30:00Z"
Filter results by date. Any parsable date format can be used.
"2025-01-01 or 2025-01-01 12:30:00 or 2025-01-01T12:30:00Z"
Filter results by date. Any parsable date format can be used.
"2025-01-01 or 2025-01-01 12:30:00 or 2025-01-01T12:30:00Z"
Filter results by date. Any parsable date format can be used.
"2025-01-01 or 2025-01-01 12:30:00 or 2025-01-01T12:30:00Z"
Filter results by date. Any parsable date format can be used.
"2025-01-01 or 2025-01-01 12:30:00 or 2025-01-01T12:30:00Z"
Filter results by date. Any parsable date format can be used.
"2025-01-01 or 2025-01-01 12:30:00 or 2025-01-01T12:30:00Z"
Filter results by date. Any parsable date format can be used.
"2025-01-01 or 2025-01-01 12:30:00 or 2025-01-01T12:30:00Z"
Filter results by date. Any parsable date format can be used.
"2025-01-01 or 2025-01-01 12:30:00 or 2025-01-01T12:30:00Z"
Filter results by date. Any parsable date format can be used.
"2025-01-01 or 2025-01-01 12:30:00 or 2025-01-01T12:30:00Z"
Filter results by date. Any parsable date format can be used.
"2025-01-01 or 2025-01-01 12:30:00 or 2025-01-01T12:30:00Z"
Filter results by date. Any parsable date format can be used.
"2025-01-01 or 2025-01-01 12:30:00 or 2025-01-01T12:30:00Z"
Filter results by date. Any parsable date format can be used.
"2025-01-01 or 2025-01-01 12:30:00 or 2025-01-01T12:30:00Z"
Get all active records that have been deprovisioned by the integration vendor
true
Filter results by date. Any parsable date format can be used.
"2025-01-01 or 2025-01-01 12:30:00 or 2025-01-01T12:30:00Z"
Filter results by date. Any parsable date format can be used.
"2025-01-01 or 2025-01-01 12:30:00 or 2025-01-01T12:30:00Z"
Can be a value of with (response will contain deleted items as well), only (will contain only deleted items), or any arbitrary value (will contain only not deleted items).
The collection of DirectoryUserDetailedResponseData
"drusr_01hq8xyzabc123def456ghi789"
The state of the directory user
staged The record is staged and is only visible to administrators or in the API. Since Directory Users are managed by Directory Identities with your primary integration, this usually indicates that the user is staged and will be activated or onboarded soon. Staged users are not included in ruleset manifests until they are active users. |
active The record is active. |
expiring The expires_at value is set in the future for the record. You can run the activate action to remove the scheduled expiration. |
expired The expires_at value is in the past and the record was deactivated. |
suspended The record is temporarily suspended. This reflects the state of the primary Workspace Integration. |
deactivated The record was deactivated in the primary Workspace Integration. |
staged, active, expiring, expired, suspended, deactivated "active"
The ID of the manager
"drusr_01kam9z5z71f7r4hhrm2ydxkhn"
Whether or not the user is a people manager with direct reports
true
The first (given) name of the user
"Dade"
The last (family) name of the user
"Murphy"
The first and last name of the user
"Dade Murphy"
The email address of the user
"dmurphy@redshirt.systems"
The username of the user. Unless overridden, this is usually the email address handle
"dmurphy"
The badge ID number of the user. This value is dynamically obtained from the primary integration based on the badge_id_profile_key
The employee ID number of the user. This value is dynamically obtained from the primary integration based on the employee_id_profile_key
An alternative/secondary employee ID number of the user. This value is dynamically obtained from the primary integration based on the employee_alt_id_profile_key
The timestamps for the directory user record
The user's organization metadata based on their dimension attributes
{
"cost_center": "CC-1234",
"department": "Infrastructure",
"division": "Engineering",
"title": "Senior Engineer"
}The user's custom key/value metadata added by someone or automation in your organization
{
"custom_field_1": "value1",
"employee_type": "full-time",
"desk_number": "42"
}Counts of related resources for the directory user
Related resources for the directory user. Use include parameter with a comma separated list of resources to fetch related data
API hyperlinks related to the directory user record