Overview

The Plext API is the canonical surface for any server, job, or integration that needs to read or write notes. Bearer-token-only by design — no cookies cross the API host.

Base URL

https://api.plext.com/v1

Authentication

Every request carries Authorization: Bearer <token>. Two token types:

• API keys (plxt_...) — long-lived, workspace-scoped, for servers and CI. Mint one at plext.com/<your-workspace>/settings → API keys → New key.
• OAuth session JWTs — short-lived, for the CLI and MCP clients. Issued by plext login (CLI) or the standard MCP authorize flow.

See Authentication for the full reference — capability model, plex scoping, revocation.

Conventions

• JSON only. All requests and responses are application/json.
• Timestamps are RFC 3339 UTC: 2026-04-23T14:30:00.000Z. Always.
• IDs are prefixed and opaque: note_<uuid>, plex_<uuid>, member_<uuid>, key_<uuid>, ws_<uuid>, session_<uuid>. Treat as strings.
• Single-resource envelope is flat at the top level with an object discriminator: { object: "note", id, ... }.
• List envelope is { object: "list", data: [...], has_more, next_cursor }. Cursor pagination via starting_after=<id>.
• Error envelope is { error: { code, message, param?, request_id } }.

Headers

Every response carries:

• X-Request-ID: req_... — include when filing bugs.
• X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset — see Rate limits.

Where to next