Authentication

​

Where the credentials come from

• API key - created in your Engini account settings at app.engini.io. Sign in to the app however you like - email/password or OAuth (Google, Microsoft, GitHub) - then create a key. The CLI’s engini login opens this page for you on a TTY.
• Bearer JWT - the session token Engini issues when you sign in (including via the OAuth providers above). It’s what the web app itself uses; you can pass it to the SDK (token=) or API for short-lived, user-scoped calls.
• OAuth apps - third-party applications (and MCP clients) can obtain Engini Bearer tokens programmatically through the standard OAuth 2.1 authorization-code flow: see OAuth apps.

​

Base URL

https://api.engini.io/v1

​

Verify a credential

curl https://api.engini.io/v1/auth/whoami -H "x-api-key: $ENGINI_API_KEY"

​

In the SDKs

from engini import Engini

client = Engini()                      # ENGINI_API_KEY (preferred) or ENGINI_API_TOKEN
client = Engini(api_key="eng_...")     # explicit API key  -> x-api-key header
client = Engini(token="...")           # explicit PAT      -> Authorization: Bearer

import { Engini } from "@engini/sdk";

const client = new Engini();                    // ENGINI_API_KEY (preferred) or ENGINI_API_TOKEN
const client2 = new Engini({ apiKey: "eng_..." });
const client3 = new Engini({ token: "..." });

​

Failures