SCIM test server

Use scim.dev when you need a SCIM 2.0 test server before connecting a real identity provider or production application. The playground gives developers a safe SCIM API endpoint for creating users, updating groups, testing filters, and checking how provisioning requests should look.

A test server is useful when you are building a SCIM client, debugging an identity provider setup, preparing a demo, or learning the protocol for the first time. You can send requests to the hosted API, inspect responses in the playground, and reset or regenerate test data without touching production users.

What you can test

• Create, read, update, patch, and delete SCIM User resources.
• Create and manage SCIM Group resources and memberships.
• Discover supported endpoints with /ServiceProviderConfig, /ResourceTypes, and /Schemas.
• Try .search, pagination, filtering, and sorting behavior.
• Send bulk requests and test ETag-based concurrency handling.
• Connect applications such as Microsoft Entra ID, Okta, SailPoint, OneLogin, and Omada.

Hosted SCIM endpoint

The hosted base URL is:

https://api.scim.dev/scim/v2/

Most requests require a bearer token. Create an API key and send it in the Authorization header:

Authorization: Bearer YOUR_API_KEY

Fastest way to start

1. Open the SCIM Playground.
2. Create or inspect test users with the Users endpoint.
3. Add test groups with the Groups endpoint.
4. Try request examples from SCIM API examples.
5. Connect your identity provider with one of the application guides.

When to use a test server instead of production

Use a SCIM test server while you are still validating request shape, attribute mappings, group push behavior, and error handling. Move to production only after your integration handles pagination, PATCH operations, duplicate users, disabled users, and group membership changes consistently.

For a structured launch path, follow the SCIM implementation checklist.