API Keys

Every request that manages your own resources authenticates with an API key, managed entirely from the dashboard.

Manage your keys from the dashboard's API health & keys page — there's no public REST endpoint for creating or deleting keys, since you'd need a key already to call one (the dashboard uses your logged-in session instead).

• Each key has a required name and an optional description — use these to note which site or integration it's for.
• A key's raw value is only ever shown once, right when you create it. Copy it immediately; if you lose it, delete the key and create a new one. Every other view (the dashboard list, GET /me) shows only a masked form like qna_XXXX••••••XXXX.
• Deleting a key immediately stops it from authenticating — nothing else on the account is affected.
• A key can optionally be scoped to one site — a site-scoped key can only see and manage that site's resources.

Get your account info

curl -H "X-API-Key: qna_..." https://qnaapi.com/api/v1/me

{
  "data": {
    "id": 1,
    "name": "Ada Lovelace",
    "email": "ada@example.com",
    "api_keys": [
      {
        "id": 1,
        "name": "Default",
        "description": null,
        "masked_key": "qna_XXXX••••••XXXX",
        "last_used_at": "2026-08-21T03:05:56.000000Z",
        "created_at": "2026-08-14T22:44:34.000000Z"
      }
    ],
    "created_at": "2026-08-14T22:44:34.000000Z"
  }
}