Skip to main content
Nudgen now supports developer access through Personal Access Tokens (PATs). Use the same token for the REST API, the MCP server, and agent workflows.

​
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

  1. Open nudgen.net.
  2. Go to Settings -> API Keys.
  3. Create a Personal Access Token.
  4. Copy the token once and store it securely.
Use the token in the standard bearer header:

​
REST API

Use the REST API when you want conventional HTTP endpoints for contacts, campaigns, brand settings, and AI draft generation.
Common endpoints include:

​
MCP server

Use MCP when an AI agent can call tools directly instead of hand-coding REST requests. The MCP endpoint is:
The server card is available at:
MCP uses the same bearer PAT as the REST API.

​
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 scheduledAt values for tests when you do not want to send immediately.