Skip to main content

API Keys

API keys are the simplest way to authenticate with Gumnut. They’re ideal for server-side applications, scripts, automation, and CI/CD pipelines.

Creating an API Key

  1. Log into the Gumnut Dashboard
  2. Navigate to API Keys
  3. Click Create API Key
  4. Name your key descriptively (e.g., “Production Server”, “Development”)
  5. Choose what the key is allowed to do:
    • View only
    • View, add, and edit
    • View, add, edit, and move to trash (the default)
    • Full access — also permits permanent deletion
  6. Choose which libraries it can reach — All current and future libraries, or Selected libraries (only the ones you pick; new libraries aren’t added automatically)
  7. Copy and securely store the key
Scope each key to the least authority the integration needs. Creating keys through the REST API additionally lets you combine actions freely rather than picking one of the presets above — read is always required, and at least one action must be set.
API keys are shown only once when created. Store them securely in environment variables or a secrets manager. Never commit API keys to version control.

Using API Keys

Include your API key in the Authorization header as a Bearer token:

TypeScript SDK

Python SDK

Node.js with axios

Managing Keys

View and manage API keys in the dashboard:
  • See creation date and last used time
  • Track usage statistics
  • Revoke keys instantly

Error Handling

401 Unauthorized — Invalid or expired API key:
Solutions:
  • Verify the key is copied correctly (should start with apikey_)
  • Check it hasn’t been revoked in the dashboard
  • Ensure you’re using the correct environment’s key
403 Forbidden — Insufficient permissions:
429 Too Many Requests — Rate limit exceeded. See Rate Limiting for details.