Install Jentic One Beta

Connect the Get a Newsletter API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Get a Newsletter 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%2Fgetanewsletter.com%2Fgetanewsletter" | 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%2Fgetanewsletter.com%2Fgetanewsletter" | 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 Get a Newsletter API.

Upsert customer contacts into Get a Newsletter using email as the natural key

Maintain mailing lists and add or remove subscribers in response to product or CRM events

Retrieve campaign reports to feed open and click rates back into analytics dashboards

GET STARTED

Start building with Get a Newsletter API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Get a Newsletter API for, with concrete tasks.

★ CRM-to-List Synchronisation

Marketing teams want a customer's CRM segment to drive their newsletter membership automatically - for example, putting all paying customers on a 'customers' list and all trial users on a 'trials' list. The Get a Newsletter API supports upsert by email on contacts and add-to-list on subscribers, so a recurring sync job can keep the list aligned with the CRM segment without duplicates.

For each contact in the CRM 'customers' segment, call `PUT /contacts/{email}/` to upsert and `POST /lists/{hash}/subscribers/` to add to the customer list.

Transactional Subscribe Flow

When a user signs up to a marketing list on a website, the front-end captures the email and the backend needs to create the contact and add them to a chosen list. The API's contact creation and subscriber addition endpoints support this flow with predictable responses, and the upsert pattern via PUT means re-submissions don't create duplicates.

On form submission, call `PUT /contacts/{email}/` then `POST /lists/{hash}/subscribers/` to subscribe the user to the chosen list.

Campaign Report Pipeline

Analytics teams want campaign open rate, click rate, and bounce data alongside web analytics in a single warehouse. The API's reports endpoints expose campaign-level metrics so a daily job can pull report records and load them into a destination such as BigQuery or Snowflake for combined dashboards.

Call `GET /reports/` for new reports since yesterday and `GET /reports/{id}/` for each report ID, then load the records into a warehouse table.

Agent-Driven Newsletter Subscription

An AI agent assisting a customer can subscribe them to the right list when they ask 'sign me up for product updates'. Through Jentic, the agent discovers the subscriber-add endpoint, executes it with the customer's email, and replies with confirmation - without ever holding the API key.

Resolve the customer's email and the requested list slug, then call `POST /lists/{hash}/subscribers/` via Jentic and confirm the success response to the customer.

Key Endpoints

25 endpoints — jentic publishes the only available openapi specification for get a newsletter api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

PUT

/contacts/{email}/

Upsert a contact by email

POST

/lists/{hash}/subscribers/

Add a subscriber to a mailing list

DELETE

/lists/{hash}/subscribers/{email}/

Remove a subscriber from a list

GET

/lists/

List all mailing lists

GET

/reports/{id}/

Get a specific campaign report

POST

/senders/{id}/request_confirmation/

Request sender email confirmation

PUT

/contacts/{email}/

Upsert a contact by email

POST

/lists/{hash}/subscribers/

Add a subscriber to a mailing list

DELETE

/lists/{hash}/subscribers/{email}/

Remove a subscriber from a list

GET

/lists/

List all mailing lists

GET

/reports/{id}/

Get a specific campaign report

POST

/senders/{id}/request_confirmation/

Request sender email confirmation

Why Jentic?

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

Setup

Wiring the Get a Newsletter API by hand means setting up its Authorization-header token, mapping contact, list, subscriber, and report calls to the right paths, and handling the trailing-slash conventions yourself. Through Jentic you install once, import Get a Newsletter from the API Directory, store the token once, and your agent calls it.

Permission scoping

Get a Newsletter puts the list hash in the URL path (/lists/{hash}/subscribers/), so a rule can pin your agent to one list: it can add subscribers to that list and nothing else. You choose the operations it may call, so destructive ones like removing a subscriber are not included unless you add them.

Credential isolation

Your Get a Newsletter token is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'add a subscriber to a mailing list' or 'pull a campaign report', and Jentic returns the matching Get a Newsletter operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Get a Newsletter API through Jentic.

Why is there no official OpenAPI spec for Get a Newsletter API?

Get a Newsletter does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Get a Newsletter 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 Get a Newsletter API use?

The API uses an API token in the `Authorization` header (`tokenAuth` scheme). Through Jentic, the token is stored encrypted in the vault and injected at execution time, so agents never see the raw value.

Can I upsert a contact by email with the Get a Newsletter API?

Yes. Use `PUT /contacts/{email}/` to update or create a contact in a single call, which is the safe pattern for idempotent CRM sync.

Can I add a subscriber to a specific mailing list?

Yes. Call `POST /lists/{hash}/subscribers/` with the email to add a contact to the list identified by `{hash}`. Use `DELETE /lists/{hash}/subscribers/{email}/` to remove.

How do I retrieve a campaign report through Jentic?

Search Jentic for `get a newsletter campaign report`, load the schema for `GET /reports/{id}/`, and execute with the report ID. Jentic injects the API token from the vault.

Does the Get a Newsletter API send transactional emails?

No. The API focuses on newsletter campaigns and list management. For transactional email (password resets, receipts), use a dedicated transactional service alongside Get a Newsletter.

Can I limit what my agent is allowed to do with the Get a Newsletter API?

Yes. Because you run Jentic One yourself, your own rules decide which Get a Newsletter operations and credentials your agent may use. Since the mailing list hash sits in the URL path (POST /lists/{hash}/subscribers/), you can pin the agent to a single list so it only adds subscribers there and nowhere else. You also choose the exact operations it may call, so destructive ones like DELETE /lists/{hash}/subscribers/{email}/ stay out of reach unless you explicitly grant them.

Get a Newsletter API

Name: Get a Newsletter API
Brand: Get a Newsletter API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticMarketingEmail MarketingapiKey25 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Manage email contacts and lists, add or remove subscribers, manage verified sender identities, and pull campaign reports for the Get a Newsletter platform. Supports upsert via PUT for predictable sync workflows.

Use for: Add a new subscriber to my newsletter list, Upsert a contact by email into Get a Newsletter, Remove a subscriber from a mailing list, List all mailing lists in my Get a Newsletter account

Not supported: Does not handle transactional email, SMS, or push notifications - use for newsletter campaign list management and reporting only.

Jentic publishes the only available OpenAPI specification for Get a Newsletter API, keeping it validated and agent-ready. Get a Newsletter is a Nordic email marketing platform used to build and send newsletters, manage subscribers, and report on campaign performance. The API exposes contacts, mailing lists, list subscribers, sender identities, and campaign reports across 25 endpoints, supporting upsert via PUT for both contacts and lists. It is most often used to sync customers from a CRM or e-commerce system into segmented mailing lists and to pull campaign reports back for analytics.

Jentic One on Github View OpenAPI Document

Connect the Get a Newsletter API to your agent

Capabilities

Start building with Get a Newsletter API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Get a Newsletter API