4dem It 4Dem Api

Name: 4Dem Api
Brand: 4Dem API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingEmail Marketingbearer208 EndpointsREST

For Agents

Manage 4Dem email and SMS marketing - recipients, address books, campaigns, automation workflows, senders, content, reports, and ecommerce stores - using bearer token auth.

Install Jentic One Beta

Connect the 4Dem Api to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 4Dem 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 4Dem Api.

Manage recipients across address books - create, update, delete, search, and export contacts

Build and send email campaigns with templates, content blocks, and scheduled delivery

Run automation workflows that trigger on events, time delays, or recipient attributes

GET STARTED

Start building with 4Dem Api

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use 4Dem Api for, with concrete tasks.

★ Email Campaign Send and Reporting

Schedule a marketing email to a segment and pull deliverability metrics afterwards. Create the campaign via the campaigns endpoints, attach content, schedule the send, then call the reports endpoints (e.g. /reports/campaigns/{campaignId}) for opens, clicks, bounces, and per-domain breakdowns. This replaces dashboard clicks with a programmable workflow.

Schedule campaign 'June Newsletter' to address book 12 for tomorrow at 09:00 CET, then 24 hours after send fetch /reports/campaigns/{campaignId} and persist opens, clicks, and bounces.

Behavioural Marketing Automation

Build a workflow that triggers on a recipient attribute change, an ecommerce event, or a time delay using the workflows resource. Combine with consents and suppressions to ensure only opted-in contacts receive automated messages, and with stores resources to react to product or order events.

Create a workflow 'Cart Abandon' that triggers when a recipient leaves /carts/{cartId} non-empty for 60 minutes, sending the cart-abandon email content.

List Hygiene And Suppressions

Maintain list quality by syncing hard bounces, complaints, and unsubscribes into 4Dem suppressions, and by exporting suppressions for use in adjacent tools. The suppressions, forgottens, and consents endpoints together enforce GDPR-style deletion and audit trails for Italian senders.

Pull all hard-bounced recipients from the last 7 days, add them to the global suppressions list, and remove them from address book 12.

Agent-Driven Email Operations

Let an AI agent run the routine email programme - schedule sends, refresh bearer tokens, pull reports, and add recipients - through Jentic. The agent searches by intent, loads the schema, and executes; bearer tokens, including refresh tokens, are managed transparently by Jentic.

Through Jentic, search 'send a 4dem campaign', load the campaign-create schema, prepare and schedule the campaign, and after send fetch the report into a database.

Key Endpoints

208 endpoints — jentic publishes the only available openapi specification for 4dem, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/authenticate

Obtain a bearer token

POST

/refresh_token

Refresh a bearer token

GET

/reports/campaigns/{campaignId}

Get a campaign's performance report

GET

/addressbook/

List address books

GET

/addressbook/{addressbookId}

Get a specific address book

GET

/apikeys

List API keys

POST

/authenticate

Obtain a bearer token

POST

/refresh_token

Refresh a bearer token

GET

/reports/campaigns/{campaignId}

Get a campaign's performance report

GET

/addressbook/

List address books

GET

/addressbook/{addressbookId}

Get a specific address book

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your 4Dem access and refresh tokens are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'read a campaign report' or 'list address books', and Jentic returns the matching 4Dem operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using 4Dem Api through Jentic.

Why is there no official OpenAPI spec for 4Dem?

4Dem publishes a developer reference at api.4dem.it/open-api but no canonical OpenAPI specification with the full endpoint surface modelled. Jentic generates and maintains this spec so that AI agents and developers can call 4Dem 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 4Dem API use?

It uses HTTP bearer tokens. Obtain a token via POST /authenticate with API credentials, then send Authorization: Bearer {token} on subsequent requests. Refresh tokens via POST /refresh_token. Through Jentic, both the access and refresh tokens are stored encrypted in the vault and rotated automatically.

How do I send a campaign with 4Dem?

Build the campaign content via the contents endpoints, create the campaign on the campaigns resource, attach the address book, and schedule the send. After delivery, GET /reports/campaigns/{campaignId} returns opens, clicks, and bounces, and per-domain trends are available under /reports/campaigns/{campaignId}/domains/{activity}.

Can I send SMS through 4Dem?

Yes. The SMS endpoints support transactional and marketing SMS alongside email. Combine SMS with email workflows to run multi-channel sequences from a single provider.

How do I add a recipient to an address book through Jentic?

Run pip install jentic, then search 'add a 4dem recipient', load the recipients-create operation, supply the address book ID and recipient fields, and execute. Run it through Jentic One, the self-hosted execution layer to receive an agent API key for execution.

Does 4Dem support marketing automation workflows?

Yes. The workflows endpoints let you build trigger-based automations such as welcome sequences, cart abandon, and re-engagement campaigns. Workflows can read recipient attributes, ecommerce store data, and consent state to decide who enters the flow.

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

Yes. Jentic One runs on your own infrastructure, and your own rules decide which 4Dem operations and credentials the agent may use. Because 4Dem puts the campaign and address-book id in the URL path, such as /reports/campaigns/{campaignId} and /addressbook/{addressbookId}, you can pin the agent to a single campaign or address book. You also choose which operations it may call, so sensitive endpoints like listing API keys at /apikeys stay off limits unless you explicitly grant them.

4dem It 4Dem Api

Connect the 4Dem Api to your agent

Capabilities

Start building with 4Dem Api

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs