Official vendor OpenAPI document · agent-readyMarketingMarketing AutomationapiKey9 EndpointsREST
For Agents
Manage contact lists, add subscribers, send email campaigns, and retrieve campaign reports on the E-goi multichannel marketing platform.
Use for: I need to add a new subscriber to an E-goi marketing list, Send an email campaign to my newsletter list via E-goi, Retrieve open and click stats for a campaign I sent yesterday, List all contact lists in my E-goi account
Not supported: Does not handle SMS dispatch, push notifications, voice campaigns, or web tracking - use for E-goi list management, email campaign sending, and campaign reporting only.
E-goi is a multichannel marketing automation platform that consolidates email, SMS, push notification, voice, and web push campaigns into a single API surface. The E-goi API exposes endpoints for managing contact lists, adding and segmenting subscribers, sending email campaigns, and pulling campaign-level performance reports. It is designed for agencies and product teams that orchestrate cross-channel nurture flows and need programmatic control over list hygiene and dispatch.
Install Jentic One Beta
Connect the E-goi API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the E-goi 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.
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%2Fe-goi-api" | 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%2Fe-goi-api" | 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.
Capabilities
What an agent can do with E-goi API.
Create and curate subscriber lists for segmented marketing sends
Add, update, and remove contacts within an E-goi list
Dispatch email campaigns to a target list with subject, sender, and content payloads
Retrieve open, click, bounce, and delivery counts for a specific campaign report
Audit list metadata and contact membership before triggering a send
Use Cases
Patterns agents use E-goi API for, with concrete tasks.
★ Newsletter list onboarding
Synchronise newly registered users from a SaaS signup flow into an E-goi list so they receive welcome and onboarding emails. Each new account triggers a POST to /lists/{list_id}/contacts with the email and any custom fields, ensuring the contact is reachable for transactional and lifecycle messaging within minutes of signup.
Add a contact with email user@example.com and first_name Alex to E-goi list 12345 and confirm the contact ID returned.
Triggered email campaigns
Send broadcast email campaigns to a list when a marketing-managed event occurs, such as a product launch or webinar invite. The /campaigns/email endpoint accepts the list ID, subject, sender, and HTML body, allowing campaign dispatch directly from a workflow without using the E-goi UI.
Send an email campaign to E-goi list 12345 with subject 'Spring Sale' and the supplied HTML body, then return the campaign_id.
Campaign performance reporting
Pull engagement metrics back into a BI dashboard or weekly digest by calling /reports/campaigns/{campaign_id}. The endpoint returns counts for opens, clicks, bounces, and unsubscribes, enabling automated reporting without exporting CSVs from the E-goi web app.
Fetch the report for E-goi campaign 67890 and summarise total opens, clicks, and unsubscribes in a one-line message.
Agent-driven contact maintenance
An AI assistant can keep an E-goi list clean by responding to natural-language requests like 'remove bounced contacts' or 'add these five new leads'. Through Jentic, the agent finds the right list and contact endpoints by intent and executes the calls without the user touching the E-goi dashboard.
Given a list of five lead emails, add each to E-goi list 12345 and report how many succeeded and how many already existed.
Key Endpoints
9 endpoints — e-goi is a multichannel marketing automation platform that consolidates email, sms, push notification, voice, and web push campaigns into a single api surface.
METHOD
PATH
DESCRIPTION
GET
/lists
List all contact lists
POST
/lists
Create a new contact list
GET
/lists/{list_id}/contacts
Retrieve contacts on a list
POST
/lists/{list_id}/contacts
Add a contact to a list
POST
/campaigns/email
Send an email campaign
GET
/reports/campaigns/{campaign_id}
Get campaign engagement report
GET
/lists
List all contact lists
POST
/lists
Create a new contact list
GET
/lists/{list_id}/contacts
Retrieve contacts on a list
POST
/lists/{list_id}/contacts
Add a contact to a list
POST
/campaigns/email
Send an email campaign
GET
/reports/campaigns/{campaign_id}
Get campaign engagement report
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
E
E-goi API
- AI-Aware (B)67/100
93
Foundational Compliance62
Developer Experience & Jentic Compatibility49
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
93
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
62
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
47%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
49
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
34%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
64%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring E-goi by hand means setting up its Apikey header auth and coding the separate list, contact, campaign, and report calls yourself. Through Jentic you install once, import E-goi from the API Directory, store the API key once, and your agent calls it.
Permission scoping
E-goi puts the list id in the URL path (/lists/{list_id}/contacts), so a rule can pin your agent to one list: it can read and add contacts for that list and nothing else. You choose the operations it may call, so sending an email campaign is not included unless you add it.
Credential isolation
Your E-goi Apikey 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 Jentic by intent such as 'send a marketing email campaign' or 'add a contact to a list', and Jentic returns the matching E-goi operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using E-goi API through Jentic.
What authentication does the E-goi API use?
E-goi requires an API key passed in the Apikey HTTP header on every request. Through Jentic, the key is stored encrypted in the vault and never enters the agent's context - agents receive a scoped token that authorises a specific operation.
Can I send email campaigns programmatically with the E-goi API?
Yes. POST /campaigns/email accepts the target list_id, subject line, sender details, and HTML body, and returns a campaign identifier. Tracking, opens, and clicks are reported back via /reports/campaigns/{campaign_id}.
What are the rate limits for the E-goi API?
The OpenAPI spec does not expose a fixed rate limit. E-goi typically applies per-account throttling on campaign dispatch and contact writes - consult your account settings or contact E-goi support for the limits applied to your plan.
How do I add contacts to an E-goi list through Jentic?
Search Jentic for 'add contact to e-goi list', load the schema for POST /lists/{list_id}/contacts, then execute with the list_id and contact payload. The full flow is: pip install jentic, then await client.search, await client.load, await client.execute.
Does the E-goi API support SMS or push campaigns?
This OpenAPI spec covers list management, contacts, email campaigns, and campaign reports. SMS, voice, and push channels are part of the broader E-goi platform but are not exposed by this 9-endpoint surface.
Can I limit what my agent is allowed to do with the E-goi API?
Yes. Because you run Jentic One yourself, your own rules decide which E-goi operations and credentials the agent may use. Since the list id sits in the URL path, such as /lists/{list_id}/contacts, you can pin the agent to a single list so it only reads and adds contacts there and touches nothing else. Sending an email campaign through POST /campaigns/email is excluded until you explicitly grant that operation.
GET STARTED