Skip to main content

POST /api/zeq-auth/session-key/mint

own row), so this never invalidates the key the web app already stored.

Auth: v3 cookie (zeq_auth_token) OR Bearer JWT (same as session-key). Response: 200 { ok, slug, machine_id, api_key, key_prefix, scope } · 401 · 40

MethodPOST
Path/api/zeq-auth/session-key/mint
Feature areaZeq Auth (OIDC broker)
TagOther
Authpublic (no key)
Tiercomputation (public)

Parameters

This operation publishes no path, query or header parameters.

Request body

Optional. Content type: application/json.

The node publishes this body as a free-form JSON object — no field schema is exposed in openapi.json. Send the fields the summary above describes; the endpoint validates them and refuses rather than guessing.

Responses

StatusMeaning
200OK
401Missing or invalid credentials
404Not found
500Server error

401 body

FieldTypeRequiredDescription
okboolean — one of falseyes
errorstringnoHuman-readable message.
codestringnoStable machine-readable code, e.g. ADMIN_REQUIRED, INVALID_ZID, ZID_NOT_LINKED.

404 body

FieldTypeRequiredDescription
okboolean — one of falseyes
errorstringnoHuman-readable message.
codestringnoStable machine-readable code, e.g. ADMIN_REQUIRED, INVALID_ZID, ZID_NOT_LINKED.

500 body

FieldTypeRequiredDescription
okboolean — one of falseyes
errorstringnoHuman-readable message.
codestringnoStable machine-readable code, e.g. ADMIN_REQUIRED, INVALID_ZID, ZID_NOT_LINKED.

Call it

curl -sS -X POST https://zeq.me/api/zeq-auth/session-key/mint \
-H "Content-Type: application/json" \
-d '{}'

Generated from the live OpenAPI description (https://zeq.me/openapi.json, spec version 1.287.0) by scripts/generate-reference.mjs. Do not edit — this file is rewritten on every run.