Apigami
Overview
OpenAPI JSONConnect applications to users' browsers with explicit, per-site permission.
Apigami API 0.1.0
Section titled “Apigami API 0.1.0”Your user installs Apigami once and approves, site by site, what your service may do. From then on your server calls this API; the request runs in the user’s browser and only the response comes back. Authenticate with an API key from the dashboard, as a Bearer token. The routes that create, write, deploy and publish your team’s applications take a member’s credential instead: an AI assistant without a browser gets one with an agent sign-in (POST /v1/device/code). Human-readable guide: https://www.apigami.com/docs/ — model-readable: https://www.apigami.com/llms.txt
Authentication
Section titled “Authentication”apiKey
Section titled “apiKey”An API key created in the dashboard (https://app.apigami.com). Shown once; revocable at any time.
Security scheme type: http
personalAccessToken
Section titled “personalAccessToken”A personal access token of a member of your team, or the access token of their signed-in dashboard session (https://app.apigami.com). The dashboard does not create personal access tokens: an AI assistant uses an agent token instead. It manages your team’s applications; it never calls one.
Security scheme type: http
agentToken
Section titled “agentToken”An agent token, apigami_agent_…, what an agent sign-in yields (POST /v1/device/code, https://www.apigami.com/docs/mcp/#agent-sign-in): 90 days, listed and revocable by the person in their account. It opens the MCP server and the routes that build your team’s applications, like the OAuth token of a member’s MCP client, and never a route that manages the team, its keys or its webhooks.
Security scheme type: http