GET https://xquik.com/api/v1/api-keys
Audit Xquik API keys before X (Twitter) automation
List every Xquik key registered to the signed-in account. Review keys before running tweet searches, follower exports, webhooks, monitors, or X writes. This endpoint returns key inventory metadata. It never returns a complete API key. Useid for revocation and prefix for safe identification.
The key list answers 6 operational questions.- Which named Xquik keys exist on this account?
- Which keys are active or revoked?
- What can each key call, and when does it expire?
- How many credits did each key spend this month, against which budget?
- When did each key last authenticate a request?
- Which key ID should a rotation workflow revoke?
Free. This endpoint does not consume credits.
Read the API key inventory
Treat the response as an account credential inventory. Never treat it as a secret recovery endpoint.lastUsedAt is optional. Its absence means Xquik recorded no authenticated use.
Xquik refreshes it at most once a minute.
As a result, it can trail the latest call by up to 60 seconds.
It does not prove that a deployment no longer needs the key.
monthlySpentCredits counts the credits charged for calls with the key this
UTC month. It starts again at 0 each month. New calls that don’t fit the budget
get 403 api_key_budget_reached. Raise or remove the budget with
Update API key to unblock the key sooner.
Check scheduled jobs before revoking a quiet key. A monthly follower export
can remain valid without recent requests. Confirm the owner and workload first.Distinguish Xquik keys from official X credentials
An Xquik API key starts withxq_. It authenticates requests to Xquik routes.
It is not an official X (Twitter) API key or X developer bearer token.Official X documentation separates application keys from bearer tokens. Read
its authentication overview
when integrating directly with the X developer platform.
Use Xquik authentication for Xquik request
headers. Use this list endpoint only for Xquik credential inventory.
Rotate an Xquik API key
Create the replacement before revoking the current key. This overlap prevents failed tweet, follower, webhook, and monitor requests.- List keys and record the current
id,name, andprefix. - Create a replacement key with a clear name.
- Store the returned
fullKeyin an approved secret manager. - Update one deployment without logging the replacement value.
- Send a planned Xquik request from that deployment.
- List keys and verify the replacement
lastUsedAtvalue. - Revoke the old key by its exact
id. - List keys again and confirm the old key is inactive.
isActive is true and expiresAt is missing or ahead.
Set expiresInDays when you create a key so a
forgotten key expires. Give a workload that only reads X (Twitter) data a paid_reads
key.Common X API key questions
Can I recover my full Xquik API key?
No.GET /api-keys returns only a safe prefix. The creation response returns
fullKey once. Create a replacement when the stored secret is unavailable.Can an API key list other Xquik keys?
No. This management endpoint requires a same-origin dashboard session. Anx-api-key header or OAuth bearer token cannot authorize the request.How do I check which Xquik key is active?
Match the deployed key prefix withprefix. Then check isActive. Never print
the complete deployed key during this comparison.What does a missing last-used time mean?
The key has no recorded authenticated request. It may be new or unused. Check the intended workload before revocation.Does this endpoint list official X (Twitter) API keys?
No. It lists Xquik keys for Xquik endpoints. Manage official X developer credentials in the X developer console.Headers
Query parameters
Response
200 OK
400 Invalid cursor
{ "error": "invalid_input", "message": "Cursor invalid. Use nextCursor from the previous page, or omit it to start over." }
The cursor is not one this list returned. Send the nextCursor of the previous page, or omit it.401 Unauthenticated
Missing, expired, or invalid dashboard session cookie.429 Rate limited
{ "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 1 }
Too many requests. Wait for the Retry-After header before retrying.API key listing requires a same-origin dashboard session. API keys and OAuth
bearer tokens cannot list account keys.Related. Create API Key · Update API Key · Revoke API Key
Response examples
- 400
{ "error": "invalid_input", "message": "Invalid input. Check the request body." } - 401
{ "error": "unauthenticated", "message": "Authentication required. Provide a valid API key or bearer token." } - 403
{ "error": "session_required", "message": "API keys & OAuth tokens cannot use this route. Sign in at dashboard.xquik.com/account instead." } - 429
{ "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 60 }