API overview

Everything in Jobably — the app, the extension, the MCP server — drives one REST API at api.jobably.com.

• Interactive reference: api.jobably.com/docs
• OpenAPI 3.1 spec: api.jobably.com/openapi.json

The OpenAPI document is not yet the whole API

It currently describes the meta endpoints (/v1/version, /v1/status) only. Every other route works and is stable — it is the machine-readable description that is incomplete, not the API.

If you are building an agent, the MCP tool reference is the complete machine-readable surface: it is generated from the running server, covers every capability, and documents every argument. If you are calling REST directly, this page and the guides are authoritative until the spec catches up.

Auth

• Session cookie — issued at sign-in; used by the app.
• Personal access token — Authorization: Bearer jbly_pat_…, scoped (read, write, ingest), created and revoked in app Settings. Token management itself is session-only: a stolen token cannot mint more tokens, plant provider keys, or delete the account.

Conventions

• Versioned under /v1; JSON everywhere.
• Errors are RFC 9457 application/problem+json with a stable type URI — branch on status and type, not message strings.
• Async AI work (tailor, revise, prep, scoring) returns 202 with an operation id; poll /v1/operations/:id or stream /v1/operations/:id/events (SSE).

Typed clients

The app’s own client is generated from the served spec with openapi-typescript — the same spec is available to you at the URL above.