canonical: https://jentic.com/apis/yespo.io

# Yespo APIs

Yespo (formerly eSputnik) is an omnichannel customer data and messaging platform. Its APIs let agents manage contacts and contact groups, send email, SMS, mobile push, Viber, and Telegram messages, run broadcasts, trigger events, track orders, and read campaign activity. Across two APIs the platform exposes 112 operations, all secured with HTTP basic authentication.

## For AI agents

An agent can add, update, search, and delete contacts, manage contact group membership, import contacts in bulk, trigger events, and send or broadcast omnichannel messages across email, SMS, push, Viber, and Telegram. It can also read contact activity and campaign data to drive follow-up workflows.

## Scope

Use for: Managing Yespo contacts and groups and sending omnichannel messages across email, SMS, push, Viber, and Telegram from an agent workflow

Not supported:
- payment processing
- developer tooling
- custom template design
- deliverability infrastructure hosting

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| Yespo API | crm | 100 | Programmatically add or update a contact, delete contact by external id. |
| Yespo (eSputnik) Marketing API | marketing | 12 | Programmatically add or update a contact, get a contact by id. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Full omnichannel contact and messaging surface including email, SMS, push, Viber, Telegram, broadcasts, events, and account operations | yespo-api | Exposes 100 operations spanning the entire platform, the widest coverage of the two APIs. |
| Focused contact and marketing operations such as importing contacts, managing groups, triggering events, and reading contact activity | marketing-api | A smaller 12-operation surface centered on contacts, groups, and campaign activity. |
| Add or update a single contact record | yespo-api | Both APIs support this, but the main API adds bulk, file import, and subscribe operations around it. |

## Cross-API use cases

### Sync contacts then message them

Import or update a contact through one Yespo API and reach the same contact through the other, keeping the customer record and outbound messaging in one account.

Example prompt: Add or update the contact via POST /v1/contact on one API, then send a follow-up message to that contact through the other.

### Group membership driven campaigns

Manage contact group membership on the marketing surface and drive broader messaging and broadcasts from the main platform surface for the same audience.

Example prompt: Add contacts to a group via POST /v1/group/{groupId}/contacts, then trigger a broadcast or message to that segment.

### Activity based follow-up

Read a contact's recorded activity on the marketing API and act on it through the main API by subscribing, updating, or messaging the contact.

Example prompt: Fetch activity via GET /v1/contact/{contactId}/activity, then subscribe or update the contact through the main API based on the result.

## Why Jentic

- **Setup:** Wiring Yespo by hand means configuring HTTP basic auth against two base URLs and working through a large contact and messaging surface yourself. Through Jentic you install once, add the Yespo APIs from the Jentic directory, store the credential once, and your agent calls either API.
- **Permission scoping:** Yespo puts contact and group ids in the URL path, so your own rules in your Jentic One instance can pin an agent to specific records or groups and decide which operations it may call. Destructive operations like deleting a contact or bulk imports are only available if you allow them.
- **Credential handling:** Your Yespo basic auth credential 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, and the same credential covers both APIs.
- **Discovery method:** Agents search the Jentic directory by intent such as 'add or update a contact' or 'add contacts to a group', and Jentic returns the matching Yespo operation with its input schema so the agent calls the right endpoint across either API without browsing the reference docs.

## Related vendors

- **Mailchimp** — Email marketing and audience management platform, an alternative for contact-based campaigns.
- **HubSpot** — Combines CRM contact management with marketing messaging, overlapping both Yespo surfaces.
- **Twilio** — Programmable SMS and multichannel messaging, an alternative for the outbound channel side.
- **SendGrid** — Transactional and marketing email delivery, adjacent to Yespo's email channel.

## FAQ

### What can an agent do across the Yespo APIs?

An agent can create, update, search, and delete contacts, manage contact group membership, import contacts individually or in bulk, trigger events, and send or broadcast messages across email, SMS, mobile push, Viber, and Telegram. It can also read contact activity and campaign data to inform later steps.

### How do the two Yespo APIs differ?

The main Yespo API is the broad surface with 100 operations covering the full platform, including account, address books, broadcasts, and every messaging channel. The Yespo (eSputnik) Marketing API is a smaller 12-operation surface focused on contacts, groups, events, and campaign activity.

### Do I need separate credentials for each API?

No. Both APIs use HTTP basic authentication tied to your Yespo account, so one username and password works across both the contact and marketing surfaces.

### Is Yespo the same as eSputnik?

Yes. Yespo is the current name for the platform formerly known as eSputnik. The marketing API still carries the eSputnik name in its title, but both APIs are part of the same Yespo product.

### Which channels can Yespo send messages through?

The platform supports email, SMS, mobile push, Viber, Telegram, and App Inbox messaging, along with broadcasts to larger audiences. The main Yespo API exposes the full set of channel operations.

### Can an agent manage audience segments?

Yes. An agent can read contact groups, add contacts to a group, and remove contacts from a group, then target messaging or broadcasts at that segment across the platform.