Elaichi SCIM groups API
The SCIM groups API from Elaichi — 2 operation(s) for scim groups.
The SCIM groups API from Elaichi — 2 operation(s) for scim groups.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/elaichi-ai:elaichi-ai-scim-groups-api"
curl "https://apis.io/api/v1/apis?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Elaichi SCIM groups API
version: 0.1.0
description: 'Control-plane HTTP API for Elaichi, the MCP control plane for SaaS teams. Authenticate with an organization API token (create one in the Elaichi app under Settings → API tokens) sent as a bearer token, plus the `X-Organization-Id` header on org-scoped routes; the MCP and OAuth endpoints use their own protocols. A few actions are deliberately not available to an API token and must be done by a person in the Elaichi app: managing API and SCIM tokens, creating an organization, approving an access request, deleting an organization, and changing the two-factor requirement. The operations concerned say so. Endpoints used only by the Elaichi app itself (sign-in, consent screens, browser redirects, inbound webhooks) are not documented.'
servers:
- url: https://api.elaichi.ai
description: Production
tags:
- name: SCIM groups
paths:
/scim-group:
get:
operationId: listScimGroups
summary: List SCIM groups
tags:
- SCIM groups
responses:
'200':
description: OK
content:
application/json:
schema:
type: object
required:
- result
- next_cursor
- prev_cursor
properties:
result:
type: array
items:
type: object
additionalProperties: true
next_cursor:
type:
- string
- 'null'
prev_cursor:
type:
- string
- 'null'
'400':
description: Bad request
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'403':
description: Forbidden
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'404':
description: Not found
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'429':
description: Rate limited
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
description: Read-only view of the groups the IdP has pushed, for populating the group → role mapping picker. Groups themselves are created and deleted by the IdP through `/scim/v2/Groups`, never here. Each row carries a bounded membership summary — `member_count` plus `member_preview` (at most 5 display names) — never the membership itself; page that through `GET /scim-group/{id}/member`. Cursor-paginated. Requires `sso:view`.
security:
- bearerAuth: []
parameters:
- $ref: '#/components/parameters/OrganizationIdHeader'
- $ref: '#/components/parameters/LimitQuery'
- $ref: '#/components/parameters/CursorQuery'
- name: q
in: query
required: false
description: Case-insensitive substring match on the group's display name. LIKE wildcards are matched literally. Max 200 characters.
schema:
type: string
maxLength: 200
/scim-group/{id}/member:
get:
operationId: listScimGroupMembers
summary: List a SCIM group’s members
tags:
- SCIM groups
responses:
'200':
description: OK
content:
application/json:
schema:
type: object
required:
- result
- next_cursor
- prev_cursor
properties:
result:
type: array
items:
type: object
properties:
user_id:
type: string
description: Member user id (`usr_…`).
display_name:
type: string
email:
type:
- string
- 'null'
next_cursor:
type:
- string
- 'null'
prev_cursor:
type:
- string
- 'null'
'400':
description: Bad request
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'403':
description: Forbidden
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'404':
description: Not found
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'429':
description: Rate limited
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
description: Lists the members of a SCIM group. The membership behind a group row’s `member_count`. `display_name` is the member’s name, else email, else the bare `usr_…` id when the IdP pushed a member this organization cannot resolve — for those rows `email` is `null`, and `q` (which searches names and emails) cannot match them. Unknown group → `404`. Cursor-paginated. Requires `sso:view`.
security:
- bearerAuth: []
parameters:
- $ref: '#/components/parameters/OrganizationIdHeader'
- name: id
in: path
required: true
schema:
type: string
description: SCIM group id (`sgrp_…`).
- $ref: '#/components/parameters/LimitQuery'
- $ref: '#/components/parameters/CursorQuery'
- name: q
in: query
required: false
description: Case-insensitive substring match over member display names and emails. LIKE wildcards are matched literally. Max 200 characters.
schema:
type: string
maxLength: 200
components:
parameters:
LimitQuery:
name: limit
in: query
required: false
description: Page size. Defaults to 50. Values above 200 are silently clamped to 200 rather than rejected; a value below 1, or a non-integer, is a 400. Ignored by the endpoints documented as unpaginated.
schema:
type: integer
minimum: 1
maximum: 200
default: 50
OrganizationIdHeader:
name: X-Organization-Id
in: header
required: false
description: Target organization (`org_…`). Required for cookie/session auth on org-scoped routes; optional for API tokens, which carry their organization, and rejected when it names a different one.
schema:
type: string
CursorQuery:
name: cursor
in: query
required: false
description: Opaque cursor — pass the `next_cursor` from a previous response. Ignored by unpaginated endpoints.
schema:
type: string
schemas:
Error:
type: object
required:
- error
description: The Elaichi error envelope. The MCP OAuth endpoints under `/oauth` are the exception — they return RFC 6749 errors instead (see `OAuthError`).
properties:
error:
type: object
required:
- message
- code
properties:
message:
type: string
description: Human-readable. 5xx messages are deliberately generic.
code:
type: string
description: Stable machine-readable code, e.g. `not_found`, `subscription_required`.
details:
description: Structured detail for codes that carry one, e.g. `toolboxes_need_resolution`.
feature:
type: string
description: The gated feature, on entitlement failures.
plan:
type:
- string
- 'null'
enum:
- personal
- gold
- black
- null
additionalProperties: true
securitySchemes:
bearerAuth:
type: http
scheme: bearer
bearerFormat: session or API token
description: '`Authorization: Bearer <token>` with an org-scoped API token (`elch_{org_id}_{64 hex}`), created in the Elaichi app under Settings → API tokens. The Elaichi app itself signs in with a session cookie, which is also accepted but is not meant for integrations. Two other credential families exist and are NOT interchangeable with this one: an MCP OAuth access token (`POST /mcp` only) and a SCIM token (`/scim/v2/*` only).'
mcpOAuth:
type: oauth2
description: MCP OAuth access token, used only by `POST /mcp` — not interchangeable with `bearerAuth`. Discovered per RFC 9728/8414 at `/.well-known/oauth-protected-resource` and `/.well-known/oauth-authorization-server`.
flows:
authorizationCode:
authorizationUrl: https://api.elaichi.ai/oauth/authorize
tokenUrl: https://api.elaichi.ai/oauth/token
scopes:
mcp:read: Anything you can already see in Elaichi. Never secret values. It can also ask an admin for access to something restricted for you.
mcp:write: Create and change teams, roles, toolboxes, templates and connections, and share access.
mcp:destructive: Permanently delete data and remove access in Elaichi. This cannot be undone.
mcp:tools: Run tools from the toolboxes you choose next, deleting in your connected apps included. It can also ask an admin for access to something restricted for you.
openid: That you are signed in, and the user ID we use for you. Nothing else.
email: Your email address, and whether it is verified. Apps use this to check your domain.