> For the complete documentation index, see [llms.txt](https://docs.ggwp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ggwp.com/identity-and-access-management-iam/api-docs-scim/discovery-apis.md).

# Discovery APIs

### Overview

SCIM Discovery APIs allow identity providers (IdPs) to automatically understand the capabilities and structure of this SCIM service.

These endpoints help IdPs determine:

* Supported features (e.g., PATCH)
* Available resource types (e.g., Users)
* Schema definitions and attributes

***

### Why Discovery APIs Matter

Discovery APIs enable **automatic configuration** of SCIM integrations.

Instead of hard-coding assumptions, IdPs can:

* Dynamically detect supported operations
* Validate request formats
* Adapt to implementation-specific capabilities

***

### Available Endpoints

GGWP SCIM implementation supports the following discovery endpoints:

<table><thead><tr><th width="250.5">Endpoint</th><th>Description</th></tr></thead><tbody><tr><td><code>/ServiceProviderConfig</code></td><td>Returns supported SCIM features</td></tr><tr><td><code>/ResourceTypes</code></td><td>Lists available resource types</td></tr><tr><td><code>/Schemas</code></td><td>Returns schema definitions</td></tr></tbody></table>

### Common Characteristics

* All endpoints use `GET` method
* Responses follow SCIM standard format
* Authentication is required
* Responses include `schemas` attribute

### Notes

* These endpoints are typically called during **initial integration setup**
* They may also be used periodically for validation
* Incorrect responses can break IdP provisioning