Skip to main content

Overview

The Nudgen Developer API gives scripts, internal tools, and AI agents a predictable REST interface for working with your Nudgen workspace.

PAT auth

Authenticate REST requests with a Personal Access Token.

Campaign operations

Create campaigns, schedule launches, and read delivery stats.

Agent-ready

Give Codex, Claude Code, Cursor, and custom agents structured access.

Why this matters

A PAT lets you automate real marketing workflows without sharing your dashboard session. You can create contacts, draft campaign copy, create campaigns, and schedule sends from trusted developer tools while keeping token access revocable.

Authentication

Create a Personal Access Token from Settings -> API Keys in the Nudgen dashboard. Store it securely and pass it with every request:
Example:
PATs are shown only once. Revoke old or exposed tokens from Settings -> API Keys.

Base URL

Interactive API playground

Use the API Playground tab next to Guides for a Swagger-style playground. Each endpoint is generated from openapi.json, includes request and response schemas, and can prefill examples for cURL, JavaScript, and Python. Paste your PAT into the playground’s bearer token field before sending requests. Playground calls hit the live Nudgen API, so use test contacts and drafts unless you intend to create or launch real campaigns.

REST endpoints

Identity and workspace

Contacts

Create a contact:

Campaigns

Create a draft campaign:
Schedule an existing campaign:
Send immediately by setting sendNow to true, or by creating a campaign with sendNow: true.
Launching a campaign schedules real email. Use /api/v1/campaigns/test-send for inbox previews that should not appear as launched campaigns in dashboard stats.

Brand settings

AI draft generation

MCP server

Use Nudgen MCP when your agent supports Model Context Protocol tools. MCP uses the same Personal Access Token as the REST API, but exposes Nudgen as agent-callable tools instead of conventional HTTP endpoints.

MCP server setup

Install Nudgen MCP in Claude Code, Cursor, Windsurf, Codex CLI, or a generic MCP client.

Responses and errors

Successful responses return JSON. Validation errors return 400, expired or missing tokens return 401, insufficient plan access returns 403, missing resources return 404, and rate limits return 429. All data is scoped to the token owner’s active workspace.