Ediware API

Name: Ediware API
Brand: Ediware API
Availability: InStock

✓ Official Vendor SpecMarketingEmail MarketingapiKey19 EndpointsREST

For Agents

Manage Ediware sub-accounts, IP pools, contact lists, and automated email campaigns with an api_key query parameter on every POST call.

Install Jentic One Beta

Connect the Ediware API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ediware 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 Ediware API.

Create, list, update, and delete Ediware sub-accounts for multi-tenant email programs

Retrieve a sub-account's API key to delegate further operations to that tenant

Manage IP pools used to route outbound campaign traffic

GET STARTED

Start building with Ediware API

Explore with Jentic

View OpenAPI Document

Ediware is an email marketing platform offering campaigns, contact lists, sub-account management, and unsubscribe handling. The API exposes 19 POST endpoints covering sub-accounts (list, create, update, delete, language, sub-account API key retrieval), IP pools, automated campaign sending, contact list management (list, create, delete, insert contacts), and supporting capabilities for forms and unsubscriptions. Agencies running multi-tenant email programs use Ediware to provision sub-accounts and orchestrate sends without rebuilding sending infrastructure per client.

Use Cases

Patterns agents use Ediware API for, with concrete tasks.

★ Agency Multi-Tenant Email Provisioning

Agencies running email programs for many clients need to provision sub-accounts quickly. The Ediware API exposes user_create, user_update, user_delete, user_list, and get_sub_account_api_key so the agency's onboarding tool can create a sub-account, capture its API key, and store it against the client record. The agency can then operate either as the master account or directly as the sub-account using its own key.

POST /user_create with the new client's details and immediately POST /get_sub_account_api_key to capture the tenant's API key for delegated calls.

Contact List Management and Bulk Imports

Marketers maintain lists per campaign segment and need to keep them current with bulk inserts. The Ediware API exposes list_list, list_create, list_delete, and list_insert so an integration can mirror lists from a CRM or warehouse. list_insert accepts contact batches so a single call covers a large import rather than per-contact loops.

POST /list_create for a new segment, then POST /list_insert with the batch of contacts pulled from the CRM.

Automated Campaign Dispatch

Once a list is in place, marketers trigger sends programmatically. POST /envoi_mail_auto runs an automated campaign email against a configured list and template, returning a send acknowledgement. This fits scheduled jobs (newsletter, abandoned cart) where the trigger lives in the marketer's stack rather than the Ediware UI.

POST /envoi_mail_auto with the listId and template reference for the weekly newsletter and confirm the send acknowledgement.

IP Pool and Sending Reputation Management

Senders running multiple segments often want to isolate sending IPs by reputation tier. POST /pools_list lists the IP pools configured on the Ediware account so an integration can assign campaigns to the right pool. This supports basic reputation hygiene without needing to manage SMTP relays directly.

POST /pools_list to enumerate available pools and pass the chosen pool to the campaign send call.

AI Agent Email Operations Assistant

An AI agent embedded in an agency tool can use Jentic to discover Ediware operations and run client onboarding, list maintenance, and campaign sends from natural-language prompts. The agent provisions a sub-account, imports contacts, and triggers a send in one chained workflow without an engineer wiring each call.

Through Jentic, search 'create ediware sub-account and send campaign', load the user_create, list_insert, and envoi_mail_auto schemas, and execute the onboarding-to-send flow.

Key Endpoints

19 endpoints — ediware is an email marketing platform offering campaigns, contact lists, sub-account management, and unsubscribe handling.

METHOD

PATH

DESCRIPTION

POST

/user_list

List sub-accounts

POST

/user_create

Create a sub-account

POST

/get_sub_account_api_key

Get a sub-account's API key

POST

/pools_list

List IP pools

POST

/list_create

Create a contact list

POST

/list_insert

Insert contacts into a list

POST

/envoi_mail_auto

Send an automated campaign email

POST

/user_list

List sub-accounts

POST

/user_create

Create a sub-account

POST

/get_sub_account_api_key

Get a sub-account's API key

POST

/pools_list

List IP pools

POST

/list_create

Create a contact list

POST

Why Jentic?

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

Credential isolation

The Ediware api_key is stored encrypted in the Jentic vault. Agents request the operation and Jentic appends the api_key query parameter at call time, so the raw key never enters the agent's context.

Intent-based discovery

Agents search natural-language intents like 'create ediware sub-account' or 'send ediware campaign' and Jentic returns the matching user_create or envoi_mail_auto operation with its input schema, so the agent can call the correct endpoint without reading Ediware's documentation.

Time to first call

Direct Ediware integration takes 1-2 days to handle the api_key query-parameter pattern, all-POST endpoint shape, and sub-account API key delegation. Through Jentic the search-load-execute flow is under an hour.

FAQs

Specific to using Ediware API through Jentic.

What authentication does the Ediware API use?

The Ediware API uses an api_key passed as a query parameter on every POST request (the apiKeyAuth scheme). Through Jentic, the api_key is stored encrypted in the Jentic vault and added to the query string at call time so it never enters the agent's context or logs.

Can I provision sub-accounts and retrieve their API keys with the Ediware API?

Yes. POST /user_create creates a sub-account and POST /get_sub_account_api_key returns its API key. The agency stores that key per client and uses it for delegated operations.

What are the rate limits for the Ediware API?

The OpenAPI spec does not declare rate limits. Ediware applies platform-level fair-use throttling on the api_http endpoint; bulk endpoints like list_insert reduce request volume by accepting many contacts per call.

How do I send a campaign through Jentic?

Search 'send ediware campaign' in Jentic, load the POST /envoi_mail_auto schema, pass the listId and template reference, and Jentic submits the send. The response confirms acceptance for delivery.

Can I bulk-import contacts into an Ediware list?

Yes. POST /list_insert accepts a batch of contacts and an existing listId. Use it to mirror a segment from a CRM or warehouse instead of inserting contacts one at a time.

Ediware API

Connect the Ediware API to your agent

Capabilities

Start building with Ediware API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs