Skip to main content
Every API request needs a valid API key. There’s no OAuth or login flow — just a simple key you include in each request.

Creating an API Key

1

Go to your API settings

Log in to snowseo.com/dashboard and go to Settings → Integrations → API.
2

Create a new key

Click Create new key and give it a name you’ll recognize later (e.g., Production Dashboard, Reporting Bot).
3

Copy the key right away

The full API key is shown only once when you first create it. Copy it immediately and save it somewhere secure (like an environment variable or a secrets manager).
If you lose the key, you can’t get it back. You’ll need to delete it and create a new one.

Using Your API Key

Add your key to the Authorization header using the Bearer format:
curl -X GET https://api.snowseo.com/v3/website-audit?url=example.com \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json"

Keeping Your Keys Safe

API keys should only be used on the server side. If you put them in browser JavaScript, anyone can see them in your network requests. Instead, make API calls from your backend or a serverless function.
Store your key in an environment variable instead of hardcoding it. Never commit secrets to version control.
# .env (don't commit this file)
SNOWSEO_API_KEY=sk_live_xxxxxxxxxxxxxxxxxxxx
It’s good practice to replace your API keys every 90 days. Create a new key first, update your environment, then delete the old one — zero downtime.
If a key was accidentally exposed (e.g., pushed to a public repo), go to Settings → Integrations → API and delete it right away. The key stops working within seconds.

Quick Test

Check that your key works by calling any endpoint:
curl https://api.snowseo.com/v3/website-ratings?url=example.com \
  -H "Authorization: Bearer YOUR_API_KEY"
If you get a 401 Unauthorized response, your key is either invalid, expired, or has been deleted.