Skip to main content
Breaking changes to the /v1 API are announced here before they ship. The OpenAPI spec is the source of truth; the SDKs are generated from it.
​
Initial public release
The Engini Developer API v1 is available to early adopters, alongside the Python and TypeScript SDKs, the engini CLI, and MCP access.Surface
  • Applications - browse the connector catalog and each application’s authentication methods
  • Connections - create and manage connections (direct credentials or OAuth), defaults, object selection
  • Tools - discover tools, read their JSON Schemas, execute them
  • Toolsets - bundle connections and permitted tools to scope an agent
  • GET /v1/auth/whoami - verify a credential
Conventions
  • JSON is camelCase throughout; applications and tools are addressed by slug, connections by integer id, toolsets by GUID
  • Offset-based pagination (offset / top) with a { items, totalCount, offset, top } envelope
  • One error envelope for every non-2xx response, with field-level details on validation failures
  • POST /v1/tools/{toolSlug}/execute returns 200 with isSuccess: false for tool-runtime failures - always branch on isSuccess
Authentication
  • API keys (x-api-key: eng_…) or Bearer JWTs; OAuth 2.1 for apps acting on behalf of Engini users, including MCP clients