Issue an API key with a scope
For the signed-in owner, in a browser session (an API key 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. The response carries the whole key once; it is not stored and cannot be shown again. scope decides what the key may do (see the APIKey schema). A request that names no scope gets a full key, as every key did before scopes could be chosen; an unknown scope is refused and nothing is issued. 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.
Request
- Base URL: https://rendry.io/api/v1
- URL: https://rendry.io/api/v1/user/api-keys
- Auth: HTTP bearer
Headers
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.
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.
Request body
Response
Issued. An APIKey whose key_value is the whole key.
Changes
No recorded changes to this operation across all 1 revision of this API.