E-goi APIs for AI Agents
MarketingMarketing AutomationMixed ProvenanceAPI keyAgent Ready
For Agents
APIs2 in catalogue
Endpoints161 indexed
AuthAPI key — 1 credential for all 2 APIs
ProvenanceMixed provenance
An agent can manage E-goi contact lists, import and tag subscribers, create and send email, SMS, push, voice, and RSS campaigns, trigger automations for selected contacts, and pull open, click, and bounce reports for a sent campaign. It can run these actions by intent without navigating the E-goi web app.
E-goi covers email, SMS, smart SMS, push, web push, voice, and RSS sends through a single provider, so an agent can drive a cross-channel journey without stitching together separate vendors. Its strength is combining list hygiene, tag-based segmentation, and automation triggers with per-channel campaign dispatch on one platform.
E-goi API Catalog
2 APIs across 1 product group. All share one credential.
Marketing2
E-goi Marketing APIRun multi-channel marketing campaigns (email, SMS, push, voice), manage contact lists and tags, trigger automations, and operate connected sites and RSS-driven sends from one API.~152 endpointsE-goi APIManage contact lists, add subscribers, send email campaigns, and retrieve campaign reports on the E-goi multichannel marketing platform.~9 endpoints
Which E-goi API should I use?
| I want to... | Use |
|---|---|
| Add subscribers, send a basic email campaign, and read campaign reports on a small endpoint surface | E-goi API |
| Run full multi-channel campaigns, tag-based segmentation, bulk imports, automations, and connected sites | E-goi Marketing API |
Install Jentic One Beta
Connect the E-goi APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the E-goi APIs, 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.
1
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%2Fe-goi.com" | sh2
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%2Fe-goi.com" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
Once connected, ask your agent something like: “run a multi-channel marketing campaign and manage contact lists with e-goi”.
What AI Agents Can Do with E-goi
Each workflow spans multiple E-goi APIs. Jentic routes each operation to the right API automatically.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring both E-goi APIs by hand means configuring the Apikey header and coding the list, contact, campaign, automation, and reporting calls across two surfaces yourself. With Jentic you install once, add E-goi from the Jentic directory, store the API key once, and your agent calls either surface.
Permission scoping
E-goi puts the list id in the URL path, so your own rules can pin an agent to one list and to specific operations. You can allow it to import and tag contacts on a single list while excluding campaign sends unless you add them.
Credential isolation
Your E-goi API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search the Jentic directory by intent such as create an email campaign or start an automation, and Jentic returns the matching E-goi operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
FAQs
Specific to using E-goi APIs through Jentic.
What can an AI agent do across the E-goi APIs?
An agent can manage contact lists and tags, import and segment subscribers, create and send campaigns across email, SMS, push, voice, web push, and RSS, trigger automations for selected contacts, and read engagement reports for sent campaigns. It can do this by describing the intent rather than navigating the E-goi web app.
How do the two E-goi APIs differ?
The E-goi API is a compact vendor-official surface of 9 endpoints for lists, contacts, email dispatch, and campaign reports. The E-goi Marketing API is a broader surface of 152 endpoints covering all channels, tags, bulk imports, automations, campaign groups, and connected sites. Use the smaller one for simple list-and-send work and the larger one for full multi-channel and automation work.
Do I need separate credentials for each E-goi API?
No. Both APIs use the same E-goi API key sent in the Apikey request header, so one credential authorises calls across the whole portfolio.
Can I run true multi-channel campaigns through these APIs?
Yes. The Marketing API exposes create and send endpoints per channel for email, SMS, smart SMS, push, web push, voice, and RSS. To sequence several channels together, configure each as a step inside an automation and start it for the target contacts.
Is there an official OpenAPI specification for E-goi?
E-goi publishes a specification for the smaller E-goi API surface. For the broader Marketing API, Jentic generates and maintains the OpenAPI specification, validated against the live API, so agents can call the full platform through structured tooling.
How does an agent find the right E-goi operation?
The agent searches by intent, such as create an email campaign or add a contact to a list, and Jentic returns the matching E-goi operation with its input schema. The agent then calls that endpoint directly without reading the reference documentation.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.