API keys
Update an Xquik API key's name or scope in place
Rename an active Xquik API key or change its scope between full access and paid reads only. It keeps its secret & expiry, and its next request uses the change.
- 200
- 400
- 401
- 403
- 404
- 429
PATCH
Update an Xquik API key's name or scope in place
Rename a key so its owner is clear, or narrow a key that only reads to
The body had neither field,
Missing, expired, or invalid dashboard session cookie.
No active API key with this ID exists on your account. A revoked key cannot change.
Too many requests. Wait for the
paid_reads. Send name,
scope, or both. The key keeps its secret, prefix and expiry.
Free. This endpoint does not consume credits.
Path parameters
string
required
The unique identifier of the API key to update.
Headers
string
required
Your signed-in dashboard session cookie,
__Host-xquik_session. API keys and OAuth tokens get
403 session_required.string
required
Must be
https://dashboard.xquik.com, sent with Sec-Fetch-Site set to same-origin. The
dashboard sends both.string
required
Must be
application/json.Body
Send at least 1 field.string
New display name, up to 100 characters. An empty name saves
"Default".string
full calls every route an API key can use. paid_reads calls paid X read routes only. Other
routes answer it with 403 forbidden. The key’s next request uses the new scope.Response
200 OK
Returns the saved key with the same fields as List API keys.400 Invalid input
scope was not full or paid_reads, or name was longer than 100
characters. Xquik changes nothing.
401 Unauthenticated
404 Not found
429 Rate limited
Retry-After header before retrying.
API key changes require a same-origin dashboard session. API keys and OAuth bearer tokens cannot
change account keys.Related. Create API Key · List API Keys · Revoke API Key