Get User by Filter name

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

Allows you to search for specific users in your organisation by filtering on user attributes such as userName, email, displayName, externalId, or active status. This is primarily used by identity providers such as Microsoft Entra ID (Azure AD) to check whether a specific user already exists in Capillary before creating or updating them.

Example request

curl --location 'https://eu.api.capillarytech.com/launchpad/api/v2/Users?filter=userName%20eq%20%22cap-demo%40gmail.com%22' \
--header 'Authorization: Bearer a7ba38a39712dff766414c43ef23dbf3c8d5138fd9db3ec3916b09a7a48da0c3' \
--header 'Accept: application/json'

Prerequisites

  • A valid SCIM bearer token for your organization, generated using the Create SCIM Token API. Pass it in the request header as Authorization: Bearer {token}.

Resource information

Pagination supportNo
Filter supportYes

Query parameters

FieldTypeRequiredDescription
filterstringYesThe filter expression used to search for users. Must follow the format attribute eq "value". Supported attributes: userName, externalId, displayName, active, emails.

Supported filter expressions

FilterExample
By usernamefilter=userName eq "[email protected]"
By external IDfilter=externalId eq "azure-object-id"
By display namefilter=displayName eq "John Doe"
By active statusfilter=active eq true
By emailfilter=emails eq "[email protected]"

Example response

{
    "schemas": [
        "urn:ietf:params:scim:api:messages:2.0:ListResponse"
    ],
    "totalResults": 1,
    "startIndex": 1,
    "itemsPerPage": 1,
    "Resources": [
        {
            "id": "50823272",
            "userName": "[email protected]",
            "name": {
                "givenName": "Cap",
                "familyName": "demo"
            },
            "displayName": "Cap demo",
            "emails": [
                {
                    "value": "[email protected]",
                    "type": "work",
                    "primary": true
                }
            ],
            "active": true,
            "schemas": [
                "urn:ietf:params:scim:schemas:core:2.0:User"
            ]
        }
    ]
}

Response parameters

FieldTypeDescription
schemasarrayIndicates the type of response being returned. Always returns "urn:ietf:params:scim:api:messages:2.0:ListResponse".
totalResultsnumberThe total number of users that matched your filter. Returns 0 if no user was found matching the filter criteria.
startIndexnumberThe starting index of the returned results. Always 1 as pagination is not supported.
itemsPerPagenumberThe number of matched users returned in this response. Same as totalResults.
ResourcesarrayThe list of users that matched your filter. Returns an empty array if no users match the filter criteria.
Resources.idstringThe unique ID assigned to the matched user in the Capillary system. Used to identify the user in subsequent SCIM operations such as update or delete.
Resources.userNamestringThe unique identifier of the matched user, typically their email address.
Resources.displayNamestringThe name displayed for the matched user on the platform.
Resources.activebooleanIndicates whether the matched user's account is currently active.
Resources.name.givenNamestringThe first name of the matched user.
Resources.name.familyNamestringThe last name of the matched user.
Resources.emailsarrayThe email addresses associated with the matched user.
Resources.emails.valuestringThe email address of the matched user.
Resources.emails.typestringThe type of email address of the matched user. Always returns work.
Resources.emails.primarybooleanIndicates whether this is the matched user's primary email address. Always returns true.

Error & warning codes

CodeTypeDescription
401ErrorAuthorization header is missing or is not a valid Bearer token.
403ErrorToken is invalid or not associated with any org.

Query Params
string
Response

Language
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json