SCIM Provisioning
SCIM 2.0 provisioning automates user and group lifecycle management from your identity provider (Azure AD, Okta, OneLogin, etc.) into Modulo.
- SCIM Users → Modulo User accounts
- SCIM Groups → Modulo Teams with membership
- Authenticated via shared Bearer token (
MODULO_SCIM_TOKEN) - Gated by
MODULO_LICENSE_KEY(Team/Enterprise tier)
Endpoints
| Endpoint | Description |
|---|---|
POST /api/v1/scim/v2/Users |
Create user |
GET /api/v1/scim/v2/Users |
List users (paginated) |
GET /api/v1/scim/v2/Users/{id} |
Get user by ID |
PUT /api/v1/scim/v2/Users/{id} |
Update user attributes |
PATCH /api/v1/scim/v2/Users/{id} |
Partial user update |
DELETE /api/v1/scim/v2/Users/{id} |
Deactivate user |
POST /api/v1/scim/v2/Groups |
Create group |
GET /api/v1/scim/v2/Groups |
List groups |
GET /api/v1/scim/v2/Groups/{id} |
Get group by ID |
PUT /api/v1/scim/v2/Groups/{id} |
Update group |
PATCH /api/v1/scim/v2/Groups/{id} |
Partial group update |
DELETE /api/v1/scim/v2/Groups/{id} |
Delete group |
All SCIM endpoints require the Authorization: Bearer <MODULO_SCIM_TOKEN> header and a valid license key.
For the full specification, see PRD §9.2 (Roles) and PRD §9.4 (Authentication).