Nudgen now supports developer access through Personal Access Tokens (PATs). Use the same token for the REST API, the MCP server, and agent workflows.Documentation Index
Fetch the complete documentation index at: https://docs.nudgen.net/llms.txt
Use this file to discover all available pages before exploring further.
Why this matters
You can connect Nudgen to scripts, internal tools, and AI agents without sharing your dashboard login. Tokens are scoped to your account and active workspace, and every request is still protected by Nudgen rate limits and workspace permissions.Create an API key
- Open nudgen.net.
- Go to Settings -> API Keys.
- Create a Personal Access Token.
- Copy the token once and store it securely.
REST API
Use the REST API when you want conventional HTTP endpoints for contacts, campaigns, brand settings, and AI draft generation.| Method | Endpoint | Purpose |
|---|---|---|
GET | /api/v1/user/me | Get the authenticated user. |
GET | /api/v1/contacts | List contacts in the active workspace. |
POST | /api/v1/contacts/add | Create a contact. |
GET | /api/v1/campaigns | List campaigns. |
POST | /api/v1/campaigns | Create a campaign. |
POST | /api/v1/campaigns/:id/launch | Launch or schedule a campaign. |
GET | /api/v1/campaigns/:id/stats | Read campaign stats. |
GET | /api/v1/settings/brand | Read brand settings. |
PATCH | /api/v1/settings/brand | Update brand settings. |
POST | /api/v1/ai/generate | Generate an email draft. |
MCP server
Use MCP when an AI agent can call tools directly instead of hand-coding REST requests. The MCP endpoint is:Safety notes
- Treat PATs like passwords.
- Revoke tokens from Settings -> API Keys when they are no longer needed.
- Campaign launch endpoints can send real email when the worker processes the queue.
- Use future
scheduledAtvalues for tests when you do not want to send immediately.