Elaichi API
API by Elaichi · rest
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.
Endpoint: https://api.elaichi.ai/
Verification: observed. Source: crawl.
Capabilities (445)
- Get authorization server metadata (RFC 8414)
- Get protected resource metadata (RFC 9728)
- Get the OpenID Connect discovery document
- List access requests (admin queue or your own)
- File an access request
- Get an access request
- Approve or deny an access request
- Withdraw an access request
- Start agent registration (auth.md service_auth)
- Get a new code for an agent registration
- List audit log events
- Get SAML service provider metadata
- List workflows
- Create a workflow
- List approvals across workflows
- Approve or reject up to 50 pending approvals at once
- Get one approval
- List who can resolve an approval
- The next approval waiting on you after this one
- Approve or reject a pending approval
- List the votes on an approval
- List Slack channels the app is in
- List Slack workspaces a trigger can use
- Suggested workflows for the caller
- List the AI models an agent step can use