List all Users
Documentation on listing Users via SCIM.
OAuth Scope required: scim.users.readUsers
Request
- Base URLhttps://ironcladapp.com/scim/v2
- URLhttps://ironcladapp.com/scim/v2/Users
- AuthAPI key in header Authorization
Query parameters
The starting index for retrieving this resource. Resources are indexed based on when they were first added to Ironclad.
Specifies the maximum number of resources to return in a single page of results.
Filters for identifying subsets of users. Filters must comply with the SCIM protocol's convention. For more details, see SCIM RFC 7644 Section 3.4.2.2.
A comma-separated list of attributes to exclude from the resources in the response.
Headers
Denotes the actor of the request. When used, the API will take into account this user's permissions and access. This or x-as-user-id is required when the associated token was produced from the Client Credentials grant or with legacy bearer tokens on select endpoints. A token produced from the Authorization Code grant (which is already scoped to a user) may also use this header to act as a different user in the same company, provided the token carries the identity.users.impersonate scope and the token's own user has been granted the API User Impersonation permission. A request that sends this header without both never acts as the named user; depending on the company's configuration it either proceeds as the token's own user or is rejected with a 403. More information about permissions.
Denotes the actor of the request. When used, the API will take into account this user's permissions and access. This or x-as-user-email is required when the associated token was produced from the Client Credentials grant or with legacy bearer tokens on select endpoints. A token produced from the Authorization Code grant (which is already scoped to a user) may also use this header to act as a different user in the same company, provided the token carries the identity.users.impersonate scope and the token's own user has been granted the API User Impersonation permission. A request that sends this header without both never acts as the named user; depending on the company's configuration it either proceeds as the token's own user or is rejected with a 403. More information about permissions.
Response
200 OK
Example response
{
"schemas": [
"urn:ietf:params:scim:api:messages:2.0:ListResponse"
],
"totalResults": 2,
"Resources": [
{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:User"
],
"userName": "alex.doe@example.com",
"name": {
"givenName": "Alex",
"familyName": "Doe"
},
"title": "Vice President",
"id": "6660d37dec0eac3deffb680e",
"emails": [
{
"value": "alex.doe@example.com",
"type": "work",
"primary": true
}
],
"active": true,
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
"department": "Legal"
},
"urn:ietf:params:scim:schemas:extension:ironclad:2.0:User": {
"departmentHead": "jane.doe@test.com",
"provider": "local"
},
"meta": {
"resourceType": "User",
"created": "2025-03-26T18:33:48.336Z",
"lastModified": "2025-03-26T18:33:48.336Z",
"location": "https://ironcladapp.com/scim/v2/Users/67e4488c605caf0d8aa2e5c6"
}
}
],
"startIndex": 1,
"itemsPerPage": 25
}Changes
No recorded changes to this operation across all 1 revision of this API.