Introduction
Everything you can do in the Elaichi app, you can do over HTTP: manage organizations, connectors, connections, toolboxes, MCP servers, members, roles, and governance.
Use it to automate setup, keep Elaichi in sync with your own systems, or build internal tooling on top.
| Base URL | https://api.elaichi.ai |
| Auth | Bearer token — see Authentication |
| Format | JSON requests and responses |
| OpenAPI | GET /schema/openapi.yml |
Your first request
Create a token under Settings → API tokens in the app, then:
curl https://api.elaichi.ai/connection \
-H "Authorization: Bearer $ELAICHI_API_TOKEN"The token is scoped to the organization you created it in.
How this reference is organized
The sidebar groups endpoints by resource — Connections, Toolboxes, MCP servers, and so on. Open a resource to see its endpoints, then an endpoint for its parameters, request body, responses, and ready-to-run examples in curl, JavaScript, and Python.
The OpenAPI document describes the same surface if you'd rather generate a client.
Before you start
- Authentication — create a token and use it
- Conventions — URL patterns, pagination, and errors
- Getting started — the product concepts these endpoints map to