API Keys

API keys authenticate your requests to the Connect API. Each key is scoped to the organization it was created in — the API resolves the organization automatically from the key.

Creating a key

1. Open Settings → API Keys in the dashboard
2. Click Create API Key
3. Copy the key — it won't be shown again

Keys start with sk_ and look like this:

sk_live_a1b2c3d4e5f6...

Using your key

With the SDK

import { createClient } from "@nilovonjs/connect";

const connect = createClient({
  apiKey: "sk_live_...",
});

The SDK handles authentication headers automatically.

With cURL

curl -X POST https://api.connect.nilovon.com/v1/messages \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "channelType": "email", "to": "user@example.com", ... }'

Security best practices

• Never commit keys to source control — use environment variables
• Rotate keys periodically from the dashboard
• Disable unused keys instead of deleting them, so you can re-enable if needed
• Use separate keys for development and production

Rate limits

API keys are rate limited to 100 requests per 60 seconds. If you exceed this limit, requests return a 429 status code. Back off and retry after a short delay.