Docs/Account and billing/API keys
Account

API keys

3 min read

API keys let your own scripts and tools call the DevThrottle API under your account. The app itself does not need one - your devices authenticate as devices - so keys are for the things you build.

Creating a key

  1. Open API Keys and create

    Name the key for what will use it - "build server", "usage script" - because usage is reported per key and a good name is what makes that report readable.

  2. Copy it now

    The full key is shown once, at creation. Copy it into your secret store; after you leave the page, only the key's name and prefix remain visible.

  3. Use it as a bearer token

    Send it in the Authorization header on API calls - see authentication for the exact shape.

Managing keys

  • Rename - click a key's name and type a new one. The name is what makes the usage report readable, so it is worth correcting when an integration changes.
  • Created and Last used - two columns on the table. Last used is how you find the key nothing has touched for months before you revoke it.
  • Per-key usage - every key's activity shows separately in Usage, so you can tell which integration is doing what.
  • Revoke - deleting a key stops it immediately, after a confirmation. If a key leaks, revoke it and create a fresh one; your other keys and devices are unaffected.
Warning
Treat keys like passwords: never commit one to a repository, and prefer one key per integration so a leak has a small blast radius and a clean revoke.
Note
Direct catalog-model calls made with a key are billed from prepaid credits - keys cannot spend money you have not loaded. Dictation, spoken replies, and the wingman are included in Pro and the 14-day Pro trial, key or no key.