Get Started

API

OAuth and HTTP integration details that are not fully represented by CLI commands.

The public API is available at https://api.epismo.ai. Product operations live under /v1; OAuth and OpenID Connect use /oauth and /.well-known endpoints. Protected product routes accept OAuth Bearer access tokens.

For normal operation, start with the CLI or MCP: they expose the same Playbook, Case, Task, Record, and Suggestion model with input validation and safer context handling. Use the HTTP API when building a product integration, OAuth client, backend service, or another surface that cannot call the CLI.

What this section covers

  • Authorization Code with PKCE, refresh-token rotation, OpenID Connect, dynamic client registration, revocation, introspection, and discovery metadata.
  • OTP exchange for first-party/manual flows and dedicated CLI/MCP token issuance.
  • HTTP status, bearer-token, workspace-context, pagination, idempotency, and optimistic-concurrency conventions.
  • A compact endpoint map for integration planning—not duplicated field-by-field schemas that can drift from the implementation.

Discover authorization endpoints from metadata instead of hard-coding them:

https://api.epismo.ai/.well-known/oauth-authorization-server
https://api.epismo.ai/.well-known/openid-configuration

In this section