canonical: https://jentic.com/apis/e-goi.com/e-goi-marketing-api

# E-goi Marketing API

Jentic publishes the only available OpenAPI specification for the E-goi Marketing API, keeping it validated and agent-ready. E-goi V3 is a multi-channel marketing platform whose API exposes endpoints for managing automations, contact lists, tags, segments, and campaigns across email, SMS, smart SMS, push, web push, voice, and RSS triggers. It is built for marketers running cross-channel journeys from one provider, and for ISVs who need to drive E-goi from a CRM, e-commerce platform, or in-app event source.

## For AI agents

Run 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.

## Scope

Does not handle accounting, e-commerce checkout, or video conferencing - use for multi-channel marketing campaigns, contact list management, and automations only.

## Capabilities

- Create and send email, SMS, smart SMS, push, web push, voice, and RSS-triggered campaigns
- Update or remove individual campaigns and group campaigns into campaign groups
- Activate, deactivate, attach or detach tags, unsubscribe, and forget contacts on a list
- Bulk-import contacts into a list and start automations for selected contacts
- Export a list of contacts for downstream segmentation or migration
- Manage connected sites that drive web push and on-site personalisation
- Retrieve all automations and the actions configured inside a specific automation

## Use cases

### Multi-Channel Onboarding Journey

When a user signs up, the application calls `/lists/{list_id}/contacts/actions/start-automation` to fire an onboarding automation in E-goi. The automation orchestrates email, SMS, and push touches over the first week using the campaign endpoints, and tags applied via `/lists/{list_id}/contacts/actions/attach-tag` drive branching steps based on activation events.

Example prompt: POST `/lists/{list_id}/contacts/actions/start-automation` with the new user's contact ID and the onboarding automation_id

### Bulk Import and Cleanup of Marketing Lists

An audience-management workflow imports a contacts CSV via POST `/lists/{list_id}/contacts/actions/import-bulk`, then runs activate/deactivate/forget actions to bring the list to a clean state. Tag attach/detach actions drive segments without rewriting the list every time the segmentation rules change.

Example prompt: POST `/lists/{list_id}/contacts/actions/import-bulk` with the contact payload, then POST `/lists/{list_id}/contacts/actions/attach-tag` to apply a 'imported-2026-06' tag

### RSS-Driven Email and Web Push

A content team configures an RSS email campaign via POST `/campaigns/email/rss` and a webpush RSS campaign via POST `/campaigns/webpush/rss`, then calls the corresponding `/actions/enable` endpoints so E-goi pulls new posts and sends them automatically. This replaces ad-hoc 'new post' notification scripts with managed campaigns the marketing team controls.

Example prompt: POST `/campaigns/email/rss` to create the campaign, then POST `/campaigns/email/rss/{campaign_hash}/actions/enable` to start RSS-driven sends

### Voice and Smart SMS Outreach

A regional campaign sends a voice message to one segment and a smart SMS to another via POST `/campaigns/voice/{campaign_hash}/actions/send` and POST `/campaigns/smart-sms/{campaign_hash}/actions/send.` Smart SMS auto-routes between SMS, RCS, and webpages based on device capability so the campaign reaches recipients on the strongest channel they support.

Example prompt: POST `/campaigns/smart-sms` with the campaign payload, then POST `/campaigns/smart-sms/{campaign_hash}/actions/send` to dispatch to the targeted list

### Agent-Driven Campaigns via Jentic

An AI marketing agent prepares a flash sale by creating an email campaign through Jentic, then sending it. The agent searches for 'create an email campaign in E-goi', loads the operation, and executes the call with subject and content - the API key is held in your Jentic One instance so the agent never sees it.

Example prompt: Use Jentic to search 'create an email campaign in E-goi', load the operation for POST `/campaigns/email`, and execute it with subject, list ID, and html content

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/campaigns/email` | Create a new email campaign |
| POST | `/campaigns/email/{campaign_hash}/actions/send` | Send an email campaign |
| POST | `/campaigns/sms` | Create a new SMS campaign |
| POST | `/lists/{list_id}/contacts/actions/import-bulk` | Bulk-import contacts into a list |
| POST | `/lists/{list_id}/contacts/actions/attach-tag` | Attach a tag to contacts |
| POST | `/lists/{list_id}/contacts/actions/start-automation` | Start an automation for contacts |
| POST | `/campaigns/push/{campaign_hash}/actions/send` | Send a push campaign |
| GET | `/automations` | List all automations |

## Key resources

- **Automations** — List automations and read the actions configured inside a specific automation; remove an automation
- **Campaigns** — List, remove, and group campaigns; create email, RSS email, push, smart SMS, SMS, voice, web push, and webpush RSS campaigns and trigger their send actions
- **Campaign Groups** — List, create, update, and delete campaign groups for organising campaigns
- **Connected Sites** — List, create, retrieve, and delete connected sites that drive web push
- **List Contacts** — Activate, deactivate, attach/detach tags, export, forget, bulk-import, unsubscribe, and start automations for contacts on a list

## Why Jentic

- **Setup:** Wiring the E-goi Marketing API by hand means setting up its Apikey header auth and coding the campaign, contact-import, tag, and automation calls across a large surface 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/actions/import-bulk`, `/lists/{list_id}/contacts/actions/attach-tag`), so a rule can pin your agent to one list: it can bulk-import contacts and attach tags for that list and nothing else. You choose the operations it may call, so sending an email, SMS, or push campaign is not included unless you add it.
- **Credential handling:** 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.
- **Discovery method:** Agents search Jentic by intent such as 'create an email campaign in E-goi' 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.

## Related APIs

- **E-goi API** — Companion E-goi API surface alongside this Marketing API in the same vendor
- **Dynosend API** — Email-focused marketing and transactional API - narrower channel scope than E-goi
- **DynaPictures API** — Generate personalised banner images for use inside E-goi email or webpush campaigns

## FAQ

### Why is there no official OpenAPI spec for the E-goi Marketing API?

E-goi does not publish an OpenAPI specification for the V3 surface. Jentic generates and maintains this spec so that AI agents and developers can call the E-goi Marketing 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 E-goi Marketing API use?

The API uses an API key passed in the 'Apikey' request header. Through Jentic, the API key is held in the encrypted vault and the agent receives a scoped execution token instead, so the raw key never enters the agent's context.

### Can I send a multi-channel campaign with the E-goi Marketing API?

Yes. The API exposes separate create + send endpoints per channel (email at `/campaigns/email`, SMS at `/campaigns/sms`, smart SMS, push, web push, voice, and RSS variants). To run multi-channel sequences, drive each channel as a step inside an automation and start it via `/lists/{list_id}/contacts/actions/start-automation.`

### What are the rate limits for the E-goi Marketing API?

The OpenAPI spec does not declare numeric rate limits. E-goi enforces plan-based send and import quotas - bulk imports run via `/actions/import-bulk` are the supported high-volume path, and large campaign sends should be triggered as automations rather than per-contact API calls.

### How do I send an email campaign through Jentic?

Run pip install jentic, search for 'create an email campaign in E-goi', load the operation for POST `/campaigns/email`, execute it with subject, list_id and html content, then call POST `/campaigns/email/{campaign_hash}/actions/send` to dispatch. Jentic injects the Apikey header per call.

### Can I trigger an automation for specific contacts only?

Yes. POST `/lists/{list_id}/contacts/actions/start-automation` accepts both an automation_id and the list of contacts to start, so you can fire the automation for a subset of the list rather than the entire audience.

### Can I limit what my agent is allowed to do with the E-goi Marketing API?

Yes. Jentic One is self-hosted by you, so your own rules decide which E-goi operations and credentials the agent may use. Because E-goi puts the list id in the URL path, such as `/lists/{list_id}/contacts/actions/import-bulk` and `/lists/{list_id}/contacts/actions/attach-tag`, you can pin the agent to a single list so it only bulk-imports contacts and attaches tags for that one list. You choose the exact operations it may call, so sending an email, SMS, push, or voice campaign is excluded unless you add those endpoints.