Install Jentic One Beta

Connect the Newsletter2Go API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Newsletter2Go API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnewsletter2go.com%2Fnewsletter2go" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnewsletter2go.com%2Fnewsletter2go" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Newsletter2Go API.

Create, read, update, and delete recipient lists for email marketing campaigns via /lists endpoints

Add new recipients or update existing ones in bulk through POST /recipients

Retrieve recipients scoped to a single list via GET /lists/{list_id}/recipients

Remove an individual recipient from a list with DELETE /lists/{list_id}/recipients/{recipient_id}

GET STARTED

Start building with Newsletter2Go API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Newsletter2Go API for, with concrete tasks.

★ Sign-Up Form to Newsletter List Sync

Marketing teams sync website sign-up forms into Newsletter2Go by calling POST /recipients with the new email address and any custom attributes. The endpoint creates or updates the recipient, and a follow-up to /lists/{list_id}/recipients confirms placement. This replaces a CSV import workflow with a per-event API call so subscribers receive their welcome email within minutes.

Add a new recipient with email new.user@example.com and first name 'Sam' to the list with id 12345

Recipient List Hygiene

Email teams keep lists clean by removing hard-bounced or unsubscribed addresses through DELETE /lists/{list_id}/recipients/{recipient_id}. Calling GET /recipients/global periodically returns the full recipient pool so an agent can compare against suppression lists from the deliverability platform and remove invalid addresses before the next send.

Remove the recipient with id rec789 from list 12345 because it bounced on the last campaign

Multi-List Campaign Setup

Campaign managers create dedicated lists per product or audience segment with POST /lists, then populate them via POST /recipients. Each list can be retrieved and updated through GET and PATCH /lists/{list_id} so naming and metadata stay aligned with campaign tracking. Listing all lists with GET /lists gives a single inventory for governance reviews.

Create a new list named 'Spring Launch Beta Testers' and add three seed recipients to it

Agent-Driven Subscriber Management

An AI agent uses Newsletter2Go through Jentic to maintain a marketing recipient base based on signals from the company's CRM and product. The agent obtains an OAuth token via POST /oauth/v2/token, then adds, updates, or removes recipients on the appropriate list whenever a downstream event - sign-up, churn, segment change - occurs. Jentic handles the OAuth refresh so the agent code stays focused on the business logic.

When a new customer is created in the CRM, add their email and name to the 'Customers' list in Newsletter2Go

Key Endpoints

11 endpoints — jentic publishes the only available openapi specification for newsletter2go api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/oauth/v2/token

Exchange OAuth credentials for an access token

POST

/lists

Create a new recipient list

GET

/lists

Retrieve all recipient lists

POST

/recipients

Create or update recipients in bulk

GET

/lists/{list_id}/recipients

Get all recipients in a list

DELETE

/lists/{list_id}/recipients/{recipient_id}

Remove a recipient from a list

POST

/oauth/v2/token

Exchange OAuth credentials for an access token

POST

/lists

Create a new recipient list

GET

/lists

Retrieve all recipient lists

POST

/recipients

Create or update recipients in bulk

GET

/lists/{list_id}/recipients

Get all recipients in a list

DELETE

/lists/{list_id}/recipients/{recipient_id}

Remove a recipient from a list

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Newsletter2Go by hand means running its OAuth2 token exchange, refreshing access tokens before they expire, and threading list and recipient ids yourself. Through Jentic you install once, import the Newsletter2Go API from the API Directory, store the client credentials once, and your agent calls it.

Permission scoping

Newsletter2Go puts the list id in the URL path (/lists/{list_id}/recipients), so a rule can pin your agent to one list: it can add and read recipients for that list and nothing else. You choose the operations it may call, so deleting a recipient is not included unless you add it.

Credential isolation

Your Newsletter2Go OAuth client credentials are stored once, encrypted, by your own Jentic One instance, which runs the token exchange and injects the access token at execution time. The secret and the token never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'add a subscriber to a list' or 'list recipients on a list', and Jentic returns the matching Newsletter2Go operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Newsletter2Go API through Jentic.

Why is there no official OpenAPI spec for Newsletter2Go API?

Newsletter2Go does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Newsletter2Go API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Newsletter2Go API use?

Newsletter2Go uses OAuth 2.0. Clients exchange credentials at POST /oauth/v2/token for a bearer access token, which is then sent on subsequent requests. Through Jentic the OAuth credentials sit in the encrypted vault and Jentic handles the token exchange and refresh so the agent never sees the long-lived secret.

Can I add multiple recipients in one call with the Newsletter2Go API?

Yes. POST /recipients accepts a payload that creates or updates recipients in bulk, which is faster than looping over per-recipient calls. For per-list scoping, use GET and DELETE under /lists/{list_id}/recipients.

How do I sync a sign-up form to Newsletter2Go through Jentic?

Search Jentic for 'add a recipient to a newsletter2go list', load the POST /recipients schema, and execute with the email and target list_id. Jentic injects the OAuth access token automatically and handles refresh, so the agent only supplies the recipient payload.

Does the Newsletter2Go API support sending campaigns directly?

The 11 endpoints in this spec cover authentication, lists, and recipients - campaign sending is not part of this surface. Use the lists and recipients endpoints to keep the audience accurate, then trigger sends from the Newsletter2Go dashboard or a campaign-specific endpoint outside this spec's scope.

Can I limit what my agent is allowed to do with the Newsletter2Go API?

Yes. Because you run Jentic One yourself, your own rules decide which Newsletter2Go operations and credentials the agent may use. Since the list id lives in the URL path, such as /lists/{list_id}/recipients, a rule can pin the agent to a single list so it only adds and reads recipients there and touches nothing else. You also choose the operations it may call, so a destructive action like DELETE /lists/{list_id}/recipients/{recipient_id} is excluded unless you explicitly allow it.

Newsletter2Go API

Name: Newsletter2Go API
Brand: Newsletter2Go API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticMarketingEmail Marketingoauth211 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Manage email marketing recipient lists and contacts on Newsletter2Go. Create lists, add or remove recipients, and authenticate via OAuth 2.0 for campaign automation.

Use for: I want to add a new subscriber to a Newsletter2Go list, Get all recipients in a specific list, Create a new email marketing list for a product launch, Remove an unsubscribed contact from a list

Not supported: Does not handle campaign creation, send scheduling, template design, or transactional email - use for OAuth, list, and recipient management only.

Jentic publishes the only available OpenAPI specification for Newsletter2Go API, keeping it validated and agent-ready. Newsletter2Go is a German email marketing platform offering campaign management and recipient list operations through a REST API. The 11 documented endpoints cover OAuth 2.0 token exchange, list create/read/update/delete, and recipient management within and across lists. Authentication uses OAuth 2.0 with a token exchange via POST /oauth/v2/token.

Jentic One on Github View OpenAPI Document

Connect the Newsletter2Go API to your agent

Capabilities

Start building with Newsletter2Go API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Newsletter2Go API