canonical: https://jentic.com/apis/yespo.io/yespo-esputnik-marketing-api

# Yespo (eSputnik) Marketing API

Yespo (formerly eSputnik) is an omnichannel marketing platform. The API allows managing contacts, sending emails and SMS, managing contact groups, triggering events, and accessing campaign analytics. The API exposes 12 endpoints secured with basic authentication.

## For AI agents

Programmatically add or update a contact, get a contact by id. Covers 12 operations with basic authentication.

## Scope

Does not handle payments, communications, or crm - use for marketing only.

## Capabilities

- Add or update a contact
- Get a contact by ID
- Delete a contact
- Import contacts
- Monitor Yespo (eSputnik) Marketing API operational status and events

## Use cases

### Marketing Operations

Use the Yespo (eSputnik) Marketing API to perform marketing operations programmatically. The API provides 12 endpoints covering core functionality including add or update a contact, get a contact by id, delete a contact.

Example prompt: Call POST `/v1/contact` to add or update a contact

### Automated Contacts Management

Automate contacts operations by combining multiple Yespo (eSputnik) Marketing API endpoints. Agents can get a contact by id and then delete a contact in a single workflow.

Example prompt: Call GET `/v1/contact/{contactId}` to get a contact by id, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Yespo (eSputnik) Marketing API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.

Example prompt: Search Jentic for 'add or update a contact', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/contact` | Add or update a contact |
| GET | `/v1/contact/{contactId}` | Get a contact by ID |
| DELETE | `/v1/contact/{contactId}` | Delete a contact |
| POST | `/v1/contacts` | Import contacts |
| GET | `/v1/contact/{contactId}/activity` | Get contact activity |
| GET | `/v1/groups` | Get all contact groups |
| POST | `/v1/group/{groupId}/contacts` | Add contacts to a group |
| DELETE | `/v1/group/{groupId}/contacts` | Remove contacts from a group |

## Key resources

- **Contacts** — Manage contacts
- **Groups** — Manage contact groups
- **Messages** — Send messages (email, SMS)
- **Events** — Trigger and manage events
- **Orders** — Manage orders

## Why Jentic

- **Setup:** Wiring Yespo Marketing by hand means setting up HTTP basic auth with your API key as the password against yespo.io/api, and handling retries yourself. Through Jentic you install once, import Yespo Marketing from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Yespo Marketing puts the contact and group ids in the URL path (`/contact/{contactId}`, `/group/{groupId}`), so a rule can pin your agent to one contact or one group: it reads that record or manages that group's membership and nothing else. You choose the operations it may call, so destructive ones like deleting a contact are not included unless you add them.
- **Credential handling:** Your Yespo Marketing 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.
- **Discovery method:** Agents search Jentic by intent such as 'add or update a contact' or 'list groups', and Jentic returns the matching Yespo Marketing operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mailchimp** — Alternative marketing API
- **Hubspot** — Alternative marketing API

## FAQ

### What authentication does the Yespo (eSputnik) Marketing API use?

The Yespo (eSputnik) Marketing API uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I add or update a contact with the Yespo (eSputnik) Marketing API?

Yes. Use the POST `/v1/contact` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Yespo (eSputnik) Marketing API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I add or update a contact through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'add or update a contact'. Jentic returns the matching Yespo (eSputnik) Marketing API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Yespo (eSputnik) Marketing API have?

The Yespo (eSputnik) Marketing API exposes 12 endpoints covering contacts, groups, messages operations.

### Can I limit what my agent is allowed to do with the Yespo (eSputnik) Marketing API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, so you can allow read and update calls like GET `/v1/contact/{contactId}` or POST `/v1/contact` while withholding destructive ones such as DELETE `/v1/contact/{contactId}.` Since Yespo puts the contact and group ids in the URL path, a rule can pin the agent to a single contact or a single group, letting it read that record or manage that group's membership and nothing else. Operations you do not grant are simply not callable.