List this account's API keys

For the signed-in owner, in a browser session. An API key cannot list, issue or revoke keys: it is refused with 401. A connector (MCP/OAuth) token is refused on every account-management door with 403 browser_session_required: a connector does MCP work, it does not manage keys. Each key is listed with its scope; the key itself is shown only as its first 12 characters. The resolved account may be selected with X-Rendry-Account; only an owner or admin browser session may administer its keys. The mode and actor are reported in each reply.

get/user/api-keys

Request

  • Base URL: https://rendry.io/api/v1
  • URL: https://rendry.io/api/v1/user/api-keys
  • Auth: HTTP bearer

Headers

X-End-Userstring

Analytics correlation only; never authorizes files or accounts. One safe ASCII value up to 64 bytes. Invalid values return 400. Persisted embedded subject takes precedence. Allowed by CORS.

X-Rendry-Accountstring

Browser/OAuth current member account selector. API keys/embed credentials are bound to their persisted account and reject another account. Omitting this header selects the browser actor personal account.

Response

Array of APIKey

idstring
namestring
key_valuestring

The whole key (sk_live_... or sk_test_...) in the create response, and ONLY there — it is not stored. The list shows the first 12 characters followed by ***.

scope'read' | 'render' | 'full'

What the key may do. read: list and read templates, presets, documents, usage, and price a batch (POST /batch-tasks/preview parses the table and quotes the run, rendering and charging nothing) — no rendering, no changes. render: everything read may, plus render_image, render_batch, render_document and preview_preset (they spend credits) — no template edits or deletions. full: everything, including creating, editing, sharing and deleting templates and files.

created_atstring
mode'live' | 'test'
actor_idstring
issued_by_actor_idstring

Changes

No recorded changes to this operation across all 1 revision of this API.