.search
The SCIM specification defines two lesser-known endpoints for performing cross-resource discovery: a top-level GET / listing and the POST /.search endpoint. These endpoints rarely surface in product documentation, yet they are invaluable when you need to query multiple resource types in one request or when you want to express complex filters that go beyond a single collection.
Note that resource specific /.search endpoints exist too, such as the one for Users in /Users/.search
POST /.search
The .search endpoint accepts a POST request with a JSON body. You can combine pagination, attribute selection, and filters across resource types. Because the request payload travels in the body, you avoid an excessively long query string, which is especially helpful when you need to express complex boolean logic.
GET /
The cross-resource GET / endpoint behaves like a lightweight catalogue. It returns a ListResponse containing resources from multiple collections, using the same shape as other SCIM list operations.
You can apply standard SCIM query parameters such as attributes, excludedAttributes, and filter to control the payload.
Filter By Resource Type
Filtering on meta.resourceType is a convenient way to scope cross-resource results. Whether you prefer POST /.search or GET /, the filter expression follows the same syntax.
The example above targets only resources classified as User. Swap the value for Group, Office, or any other resource type defined by your server.