Plans: Pro and Enterprise. Self-hosted: Enterprise license.
402 with code plan_feature_not_included; reads stay open.
Your identity provider calls the SCIM endpoints. You manage the tokens it uses in Settings → Security → Single sign-on, under SCIM provisioning, or with the token routes below. Setup guide: SCIM provisioning.
SCIM tokens
The token routes take a dashboard session (Authorization: Bearer <session-token>) from a user with the admin role or a superuser. Anyone else gets 403.
List tokens
GET /api/settings/scim/tokens
Returns every token, newest first, including revoked ones. The token value is never returned.
Generate a token
POST /api/settings/scim/tokens
201:
token is shown only in this response. Store it in your identity provider’s Secret Token field.
Revoke a token
DELETE /api/settings/scim/tokens/{id}
204 on success. 404 with token not found or already revoked (plain text) otherwise. A revoked token stops working immediately.
SCIM endpoints
Base URL:https://<your-host>/scim/v2. Send the token as Authorization: Bearer <scim-token>. Responses and errors follow RFC 7644. Errors look like this:
What the server supports (
GET /ServiceProviderConfig): PATCH yes, filtering yes (up to 200 results), bulk no, sort no, ETags no, password change no.
Users
Setting
active to false removes the user so they can no longer sign in, without erasing their data. Setting it back to true restores them.
Filters take one clause, attribute operator "value", with operators eq, co (contains), and sw (starts with) on userName, externalId, emails.value, or displayName. and, or, and not aren’t supported and return 400 with scimType: invalidFilter.
Groups
Each SCIM group is an org unit. Its members become the unit’s directory-synced members, and their roles are recalculated.
A member
value can be the Nasiko user ID from a SCIM response, or the user’s ID in your identity provider. Memberships added by hand in Nasiko are never changed by SCIM.