Skip to main content
This section is for engineers integrating Nectar into applications, pipelines, and internal tooling.

Start here

Use this order for the fastest implementation path:
  1. Get your API key
  2. Make your first API request
  3. Run sandbox testing
  4. Implement webhooks
  5. Add magic link integration (optional)
  6. Use API Reference for endpoint details

API key setup in Settings

Create keys in Settings > Organization > API Keys.
EnvironmentRecommendationWhy
SandboxCreate one key per test app/integrationIsolate test traffic and avoid shared-secret confusion
ProductionCreate separate keys per serviceSafer rotation and scoped blast radius

Rotation without downtime

1

Create a replacement key

Generate a new key before touching the current one.
2

Deploy the new key

Update your service configuration or secret manager and deploy.
3

Verify traffic

Confirm successful requests and webhook processing with the new key.
4

Delete old key

Revoke the old key only after the new key is live everywhere.

Choose your API version

VersionStatusGuidance
v2.2RecommendedUse this for all new integrations
v2.1SupportedMaintain existing integrations, plan migration
v2.0Legacy supportUse only for older integrations that cannot migrate yet
For all new integrations, start on v2.2.

Common implementation tracks

Developer FAQ

Confirm the X-API-Key header is present, your key is active, and you are using the correct environment key (sandbox vs production).
Call /ping on your target API version. A 200 response confirms the key is accepted.
Usually scope, object visibility, or incorrect resource identifiers. Verify the company context and object IDs your integration is requesting.
Treat webhook deliveries as at-least-once and build idempotent handlers keyed by event ID. Retry transient failures and log processed IDs.