Sailthru API

Name: Sailthru API
Brand: Sailthru API
Availability: InStock

✓ Official Vendor SpecMarketingEmail MarketingapiKey22 EndpointsREST

For Agents

Programmatically create or update a user profile, retrieve user profile data. Covers 22 operations with apiKey authentication.

Install Jentic One Beta

Connect the Sailthru API to your agent

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

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%2Fsailthru.com%2Fsailthru" | sh

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%2Fsailthru.com%2Fsailthru" | 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 Sailthru API.

Create or update a user profile

Retrieve user profile data

Permanently delete a user profile

Send, schedule, or update a triggered message

GET STARTED

Start building with Sailthru API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Sailthru API for, with concrete tasks.

★ Marketing Operations

Use the Sailthru API to perform marketing operations programmatically. The API provides 22 endpoints covering core functionality including create or update a user profile, retrieve user profile data, permanently delete a user profile.

Call POST /user to create or update a user profile

Automated Users Management

Automate users operations by combining multiple Sailthru API endpoints. Agents can retrieve user profile data and then permanently delete a user profile in a single workflow.

Call GET /user to retrieve user profile data, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Sailthru 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 apiKey tokens manually.

Search Jentic for 'create or update a user profile', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

22 endpoints — sailthru (marigold engage) api for email marketing automation, user profile management, campaign scheduling, content management, purchase tracking, and analytics.

METHOD

PATH

DESCRIPTION

POST

/user

Create or update a user profile

GET

/user

Retrieve user profile data

DELETE

/user

Permanently delete a user profile

POST

/send

Send, schedule, or update a triggered message

GET

/send

Retrieve triggered send information

DELETE

/send

Cancel a scheduled send

POST

/blast

Create, update, or schedule a campaign

GET

/blast

Retrieve campaign data

POST

/user

Create or update a user profile

GET

/user

Retrieve user profile data

DELETE

/user

Permanently delete a user profile

POST

/send

Send, schedule, or update a triggered message

GET

/send

Retrieve triggered send information

DELETE

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Sailthru API by hand means managing its API key, attaching it to each call against api.sailthru.com, and handling your own retries. Through Jentic you install once, import the Sailthru API from the API Directory, store the key once, and your agent calls it.

Permission scoping

The Sailthru API takes the user, send, and blast targets in the request body rather than the URL path, so scope the agent to the operations it needs, such as reading a user profile or scheduling a send, and leave out destructive ones like deleting a user or send unless the agent needs them.

Credential isolation

Your Sailthru API key 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 'create or update a user profile' or 'schedule an email send', and Jentic returns the matching Sailthru API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Sailthru API through Jentic.

What authentication does the Sailthru API use?

The Sailthru API uses an API key passed in the `api_key` query. 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 create or update a user profile with the Sailthru API?

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

What are the rate limits for the Sailthru 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 create or update a user profile through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create or update a user profile'. Jentic returns the matching Sailthru API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Sailthru API have?

The Sailthru API exposes 22 endpoints covering users, send, campaigns operations.

Can I limit what my agent is allowed to do with the Sailthru API?

Yes. Because you run Jentic One yourself, you decide which Sailthru operations the agent can call and which stored credential it uses, so you can allow read-only calls like GET /user to look up a profile or GET /send to check triggered messages while blocking the rest. When an agent needs to act, you can grant POST /user to update a profile, POST /send to schedule a message, or POST /blast to schedule a campaign, and still withhold the destructive DELETE /user and DELETE /send operations unless that agent truly needs them. The agent can only invoke the operations your own rules permit.

Sailthru API

Connect the Sailthru API to your agent

Capabilities

Start building with Sailthru API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs