Getting Started

Authentication

How to authenticate with the Nitrosend API

Authenticated API operations accept an API key or a supported user session. Account signup and email verification are public endpoints; they do not require an API key.

API Keys

Generate an API key from Settings > API Keys in the dashboard (app.nitrosend.com/my/settings/api-keys). Keys are prefixed with nskey_live_. There is no test mode: every key sends real mail.

Info

All plans, including free plans, have full access to Nitrosend MCP/API/CLI. You can create API keys on the Free plan; plan limits apply to usage volume and paid add-ons. The Free plan includes 5,000 non-expiring starter emails, then 500 free emails every month.

Using your key

Pass your API key in the Authorization header:

Authorization: Bearer <your-nitrosend-api-key>

Example

curl https://api.nitrosend.com/v1/my/account \
  -H "Authorization: Bearer nskey_live_..."
Warning

Keep your secret keys (nskey_live_…) secret. Never expose them in client-side code or commit them to version control.

Email verification and account signup

Password signup stays available to browsers and agents. Headless onboarding describes the pending → proof → activation exchange. Only a completed signup receives a session and can create API keys. Existing customers can continue signing in without a retroactive email-verification requirement.

When changing your profile email, the current email remains your sign-in address until you explicitly confirm the link sent to the new address. Confirming an email change does not issue another session or change your password.

Public keys for website forms

There is a second, restricted key type prefixed wpkey_live_…. Unlike a secret key, a public key can only create contacts and add them to your lists, so it is safe to embed directly in website source. Use it to collect signups from your site with no server and no exposed secret.

See Website Signup Forms for the full setup.