eSputnik API

Name: eSputnik API API
Brand: eSputnik API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing Automationbasic18 EndpointsREST

For Agents

Sync contacts, fire behavioural events, push orders, and trigger workflows in eSputnik to drive omnichannel email, SMS, push, Viber, and Telegram messaging.

Connect the eSputnik API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the eSputnik 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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 eSputnik API API.

Add or update individual contacts and their channel preferences in eSputnik

Bulk upload contacts from an external file and poll the import status

Fire behavioural events (cart abandonment, order placed, view) to trigger workflows

Push order data to power post-purchase and replenishment messaging

GET STARTED

Start building with eSputnik API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for eSputnik API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for eSputnik API, keeping it validated and agent-ready. eSputnik is an omnichannel marketing automation platform that delivers email, SMS, web push, mobile push, Viber, and Telegram messages. The API exposes contacts, segmentation groups, address books, behavioural events, orders, and workflows so that marketers can keep the platform's audience and triggers in lockstep with their site, app, and commerce backend. Bulk contact upload and event-driven workflow triggers cover most lifecycle messaging needs.

Use Cases

Patterns agents use eSputnik API API for, with concrete tasks.

★ Cart abandonment recovery via behavioural events

When a shopper leaves items in a cart, the storefront fires a 'cart_abandoned' event to /v1/event with the contact identifier and the cart payload. eSputnik's matching workflow picks up the event and sends a sequenced email and SMS reminder using the contact's saved channel preferences. Marketers update copy in eSputnik without touching the storefront integration.

POST to /v1/event with eventTypeKey 'cart_abandoned', the contact's externalCustomerId, and the cart line items so the corresponding eSputnik workflow runs.

Post-purchase lifecycle messaging from order data

Each completed order in the commerce backend is pushed to /v1/orders, giving eSputnik the products, totals, and shipping fields. Workflows then trigger thank-you emails, replenishment reminders, and review requests at the right cadence. Returns and cancellations can be flagged with DELETE /v1/orders to suppress those flows.

POST a new order payload to /v1/orders for each completed checkout so the post-purchase workflow fires for that customer.

Audience sync from a CRM into eSputnik segments

Operations teams keep eSputnik audiences in sync with their CRM by uploading nightly contact files via /v1/contacts/upload, polling /v1/importstatus/{sessionId} until the import finishes, and then verifying segment membership via /v1/group/{id}/contacts. The same flow handles unsubscribes, since contacts removed from the source file age out of segments as scheduled.

Upload today's contact CSV to /v1/contacts/upload, poll /v1/importstatus/{sessionId} every 30 seconds until status is finished, then GET /v1/group/{vipId}/contacts to verify the VIP segment count.

AI agent triggering targeted messaging on behalf of a marketer

A marketing agent in a chat tool takes a natural-language brief such as 'message everyone in the VIP segment about the holiday sale', looks up the segment via the groups endpoint, then either bulk-updates a tag through /v1/contacts or fires a workflow via an event. Through Jentic, the eSputnik basic auth credentials remain in the vault and the agent operates on a scoped execution token.

List groups via GET /v1/groups, locate 'VIP', then POST a 'holiday_sale' event to /v1/event for each contact returned by GET /v1/group/{id}/contacts.

Key Endpoints

18 endpoints — jentic publishes the only available openapi specification for esputnik api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v1/contact

Add or update a contact

POST

/v1/contacts

Bulk add or update contacts

POST

/v1/contacts/upload

Upload contacts from an external file

GET

/v1/importstatus/{sessionId}

Get the status of a contact import session

POST

/v1/event

Fire a behavioural event to trigger a workflow

POST

/v1/orders

Push order data into eSputnik

GET

/v1/group/{id}/contacts

List contacts in a segment

GET

/v1/workflows

List available workflows

POST

/v1/contact

Add or update a contact

POST

/v1/contacts

Bulk add or update contacts

POST

/v1/contacts/upload

Upload contacts from an external file

GET

/v1/importstatus/{sessionId}

Get the status of a contact import session

POST

/v1/event

Fire a behavioural event to trigger a workflow

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The eSputnik basic auth username/password pair is stored encrypted in the Jentic vault. Agents call operations with a scoped token; the raw credential never enters the prompt or logs.

Intent-based discovery

Agents search Jentic with intents such as 'fire a cart abandonment event' or 'bulk import contacts' and Jentic returns the matching eSputnik operation with its input schema, so the agent does not need to browse the eSputnik docs site.

Time to first call

Direct eSputnik integration: 3-5 days for auth, contact upload polling, event mapping, and error handling. Through Jentic: under an hour to make the first event call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Klaviyo API

Klaviyo is a US-headquartered ecommerce-focused marketing automation platform with similar event-driven flows.

Choose Klaviyo when targeting US/EU ecommerce brands; eSputnik has stronger CIS-region channel coverage (Viber, Telegram).

Alternative

Brevo (Sendinblue) API

Brevo offers omnichannel email, SMS, and chat with a similar contacts and events model.

Use Brevo when the team is already on the Sendinblue/Brevo SMB stack.

Complementary

Etrigue API

Etrigue provides B2B demand-generation lead and campaign tracking that complements consumer messaging in eSputnik.

Use Etrigue alongside eSputnik when the same organisation runs B2B demand-gen and B2C lifecycle messaging.

FAQs

Specific to using eSputnik API API through Jentic.

Why is there no official OpenAPI spec for eSputnik API?

eSputnik does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call eSputnik API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the eSputnik API use?

The eSputnik API uses HTTP basic authentication with the account username and an API password issued in the eSputnik dashboard. Through Jentic, that credential pair is encrypted in the vault and the agent only ever holds a scoped execution token.

Can I trigger a workflow with the eSputnik API?

Workflows are triggered indirectly by firing a matching behavioural event to POST /v1/event with the contact's externalCustomerId and the workflow's event key. The active workflow definitions can be listed with GET /v1/workflows so you can confirm which event keys are wired up.

What are the rate limits for the eSputnik API?

eSputnik does not document a fixed rate-limit number in this spec. Treat bulk endpoints (/v1/contacts, /v1/contacts/upload, /v1/orders) as the right path for large jobs and back off on any 429 response rather than retrying single-record endpoints in tight loops.

How do I bulk-import contacts to eSputnik through Jentic?

Search Jentic for 'bulk import contacts to eSputnik'. Jentic returns POST /v1/contacts/upload with the file payload schema. Execute it, then call GET /v1/importstatus/{sessionId} on a short loop until the import finishes and verify the resulting count via GET /v1/contacts.

Does the eSputnik API support push and Viber channels?

Channel routing is handled inside eSputnik based on each contact's saved preferences and the workflow design. The API exposes the inputs (contacts with channel fields, events, orders) that drive those workflows; the actual push, Viber, and Telegram delivery happens in the platform.