RaspberryPints Logo
Log inStart your taplist

Managing API Keys

The RaspberryPints Partner API lets you integrate your POS system, inventory management tools, or custom applications with your brewery data. This guide walks you through creating an API key and making your first request.

Prerequisites

  • A RaspberryPints account with an active Basic or Professional license
  • Owner access to your brewery

Navigating to API Keys

Log in to your RaspberryPints admin panel and select API Keys from the sidebar navigation. This page is where you create, view, and revoke all API keys for your brewery.

Creating an API Key

  1. Enter a descriptive name for the key (e.g., "POS Integration" or "Inventory Sync")
  2. Select the permissions your integration needs:
    • Beers: Read — List and view beer details
    • Beers: Write — Create, update, and delete beers
    • Taps: Read — List taps, view tap and session details
    • Taps: Write — Create/delete taps, tap and untap beers
    • All access — Full access to all current and future endpoints
  3. Click Create Key

Important: Your API key will only be shown once. Copy it immediately and store it in a secure location like a password manager or environment variable. If you lose the key, you'll need to revoke it and create a new one.

Authenticating Your Requests

Include your API key in the x-api-key header of every request:

curl -H "x-api-key: your-api-key-here" \
  https://api.raspberrypints.com/v1/partner/breweries/{breweryId}/beers

Finding Your Brewery ID

Your brewery ID is displayed at the top of the API Keys page in the admin panel. Click Copy to copy it to your clipboard. You'll need it for all Partner API requests.

Viewing Active Keys

The API Keys page shows all your active keys with their name, a prefix of the key value, assigned scopes, creation date, and last used date.

Revoking a Key

If a key is compromised or no longer needed, click Revoke next to the key. This immediately disables the key — any integrations using it will lose access. Revoked keys are shown in a separate section for your records.

Best Practices

  • Least privilege: Only grant the scopes your integration actually needs
  • One key per integration: Create separate keys for each system so you can revoke individually
  • Never expose keys in client-side code: API keys should only be used in server-side applications
  • Rotate periodically: Revoke old keys and create new ones on a regular schedule

Next Steps

Now that you have an API key, explore the full API reference to see all available endpoints and try them out interactively.