Skip to main content
nodepick.ai uses API key authentication for all programmatic access. Every request you make through the Python SDK or HTTP API must include a valid API key passed as a Bearer token in the Authorization header.

Getting an API Key

You generate API keys from the nodepick.ai dashboard. Follow these steps:
  1. If you don’t have an account yet, register at nodepick.ai and log in.
  2. Set up your credit card in the dashboard.
  3. In the left-hand navigation, open Developer, then go to API Keys.
  4. Click Generate and give the key a descriptive name (for example, dev or ci-pipeline).
  5. Copy and save the key immediately — it will not be shown again after you leave the page.
You can create multiple keys for different environments or applications and revoke any of them independently from the same settings page.

Using Your API Key with the Python SDK

Pass your API key to the nodepick constructor when you initialize a client:
Every SDK method called on client automatically includes your key in request headers.

Using Your API Key with the HTTP API

Include your API key as a Bearer token in the Authorization header of every HTTP request:
Replace YOUR_API_KEY with the key generated in the dashboard.

Keeping Your API Key Secure

Never commit your API key to source code or check it into version control. If a key is exposed in a public repository, revoke it immediately from Developer Settings and generate a new one.
The recommended approach is to load your API key from an environment variable at runtime:
Set the environment variable in your shell or CI environment before running your script:
For local development, store the variable in a .env file and load it with python-dotenv. Ensure .env is listed in your .gitignore file so it is never committed.

Rotating Keys

If you suspect a key has been compromised:
  1. Open Developer Settings in the dashboard.
  2. Click Generate to create a replacement key.
  3. Update your applications or environment variables with the new key.
  4. Delete the old key. Key deletion is immediate and permanent — any request sent with a deleted key returns a 401 Unauthorized error.

Common Authentication Errors

All authentication error responses return a consistent JSON payload: