---
title: SCIM 2.0 searches
description: You can cap the total number of resources that are matched by a search to prevent exhausting server resources.
component: pingdirectory
version: 11.1
page_id: pingdirectory:managing_scim:pd_proxy_scim_2_searches
canonical_url: https://docs.pingidentity.com/pingdirectory/11.1/managing_scim/pd_proxy_scim_2_searches.html
llms_txt: https://docs.pingidentity.com/pingdirectory/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: 2026-08-17T00:00:00Z
page_aliases: ["managing_scim_11_and_20_servlet_extensions:pd_proxy_scim_2_searches.adoc"]
---

# SCIM 2.0 searches

You can cap the total number of resources that are matched by a search to prevent exhausting server resources.

The configuration for each System for Cross-domain Identity Management (SCIM) *(tooltip: \<div class="paragraph">
\<p>An application-level, HTTP-based protocol for provisioning and managing user identity information. SCIM supplies a common schema for representing users and groups and provides a REST API.\</p>
\</div>)* 2.0 resource type contains a `lookthrough-limit` property that defines this limit. The default `lookthrough-limit` value is 500. If a search request exceeds the lookthrough limit, the client receives a `400` response with an error message similar to the following:

```
{
    "detail": "The search request matched too many results",
    "schemas": ["urn:ietf:params:scim:api:messages:2.0:Error"],
    "scimType": "tooMany",
    "status": "400"
}
```

To prevent this error:

* The client must refine its search filter to return fewer matches.

* You should configure paged searches as shown in [Using paged SCIM searches](pd_proxy_use_paged_scim_searches.html).