Features
API Keys
Manage API keys for SDK authentication.
An API key lets the SDK send jobs to one environment. Queuedash stores a SHA-256 hash of each key, plus its first 12 and last 4 characters so you can tell keys apart.
Create a key
- Open the project. In the environment's API Keys section, click Add
- Name it (e.g., "prod-workers") and click Create
- Copy it. It's shown once.
Formats
sk_live_...: a key for the project's default environment, the Production environment every project starts withsk_test_...: a key for any other environment
The prefix is a label. Either kind works only for the environment it was created in.
Best practices
- One key per environment
- Store in a secrets manager, not git
- Rotate on a schedule or after sharing incidents. Keys don't expire on their own.
# .env example
QUEUEDASH_API_KEY=sk_live_...Replace and revoke
- Create a new key
- Deploy the new value to your workers
- Revoke the old key: click the trash icon next to it, then Revoke
Once a key is revoked, requests made with it are rejected, and the SDK drops those batches after its retries. Replace first, then revoke.
A key can only add, update, and remove jobs in its environment. It can't read data back, or change settings, billing, or team members.