Authentication
The Miteos API supports two authentication methods:
API Keys (Recommended for integrations)
Create API keys from your API Keys page. Each key has specific scopes that control what it can access.
API keys are prefixed with mk_live_ (production) or mk_test_ (sandbox).
Available Scopes
Creating an API Key
Response:
The full key is only shown once at creation. Store it securely — it cannot be retrieved later.
JWT Tokens (For browser sessions)
Used by the web app and Desktop app. Obtained via login:
Returns:
- Access tokens expire in 60 minutes
- Refresh tokens expire in 7 days
- Use
POST /auth/refresh with the refresh token to get a new access token
Using in the Playground
In the “Try It” panel on any API reference page:
- Paste your API key in the Authorization field
- The
Bearer prefix is added automatically
- Click “Send” to make a live request to
api.miteos.com
Webhooks
Receive real-time events when tasks complete, agents need approval, etc.
Create webhooks from the API Keys page or via API:
Webhook payloads include an X-Miteos-Signature header for verification.