canonical: https://jentic.com/apis/meetmarigold.com/meetmarigold

# Meetmarigold Sailthru (Engage by Marigold) API

Jentic publishes the only available OpenAPI specification for Sailthru (Engage by Marigold) API, keeping it validated and agent-ready. Sailthru, now part of Marigold, is a customer engagement platform focused on personalised email marketing, user profiles, and lifecycle campaigns. The API exposes 13 endpoints across blasts, lists, sends, templates, and user data, letting an agent send transactional or campaign email, manage subscriber lists, look up profiles, and orchestrate templated content. It is well-suited to media and retail brands who already store user state in Sailthru and want to drive sends from external systems.

## For AI agents

Send transactional and campaign email through Sailthru, manage subscriber lists and templates, and read user profiles so an agent can drive personalised lifecycle email.

## Scope

Does not handle SMS, push notifications, or paid advertising - use for email sends, lists, templates, and Sailthru user profiles only.

## Capabilities

- Send a one-off transactional email to a single user with a chosen template
- Schedule a blast campaign to a named subscriber list with a chosen send-time
- Update a user profile with custom variables that downstream templates render
- Add or remove a user from a subscriber list to keep segments accurate
- Manage email templates including content, subject line, and from address
- Look up a user by email and inspect their lifecycle state in Sailthru

## Use cases

### Triggered Lifecycle Emails

Drive transactional and lifecycle emails from product events such as sign-up, purchase, or abandoned cart by calling Sailthru's send endpoint with the user's email and a chosen template. Sailthru renders personalisation variables server-side using the user's profile, so the calling system only needs to supply the trigger context. Lifecycle teams pair this with profile updates to keep template variables fresh.

Example prompt: Update the Sailthru user profile for jane@example.com with last_purchase_amount=49.99, then call /send with template=post-purchase-thanks for that user.

### Campaign Scheduling for Editorial Teams

Editorial teams compose a daily or weekly newsletter and schedule it to a Sailthru list at the correct send-time without logging into the dashboard. The /blast endpoint accepts subject, list, content, and schedule fields in one call, which lets a CMS or workflow tool publish the newsletter the moment editorial sign-off lands. This compresses the publish-and-schedule loop into a single API request.

Example prompt: Create a Sailthru blast targeting list=daily-newsletter with subject=Today's Headlines, html_body from the CMS export, scheduled for 2026-06-12 06:00 UTC.

### Profile-Synchronised Segmentation

Keep Sailthru user profiles in lockstep with the source-of-truth customer record so segmentation stays accurate. The /user endpoint accepts arbitrary key-value variables which downstream lists, templates, and lifecycle campaigns can target. Marketing operations teams use this to push attributes such as plan tier, churn risk, or product preferences into Sailthru on a recurring schedule.

Example prompt: Iterate over the daily customer-attribute changeset and call /user for each email with the updated plan_tier and churn_risk variables.

### Agent-Driven Re-Engagement

Hand a retention agent the ability to identify lapsed users in a list, build a personalised re-engagement send, and execute it through Sailthru without a human marketer. By calling Sailthru through Jentic the agent searches by intent, loads the schema for /list and /send, and chains the operations safely. This lifts re-engagement campaigns out of the marketer's manual queue and into autonomous execution.

Example prompt: Pull the lapsed-90d list from Sailthru, send each user a /send call with template=we-miss-you, and log the resulting send IDs.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/send` | Send a templated email to a single user |
| POST | `/blast` | Schedule a campaign blast to a list |
| POST | `/list` | Manage a subscriber list and its members |
| POST | `/template` | Create or update an email template |
| POST | `/email` | Look up or update a user by email address |

## Key resources

- **Send** — Send a transactional or templated email to a single user
- **Blast** — Schedule and manage list-targeted email campaigns
- **List** — Manage subscriber lists and list membership
- **Template** — Create and update email templates with subject, from, and HTML body
- **Email/User** — Look up and update individual user profiles by email

## Why Jentic

- **Setup:** Wiring Sailthru by hand means implementing its api_key query authentication and hand-coding each JSON send, blast, list, and template call against api.sailthru.com. Through Jentic you install once, import the Sailthru (Engage by Marigold) API from the API Directory, store the api_key once, and your agent calls it.
- **Permission scoping:** Sailthru's send, blast, list, and template operations carry their target in the request body rather than the URL path, so scope the agent to the operations it needs, such as sending a templated email or reading a list. You choose the operations it may call, so a broadcast blast is available only if you include it.
- **Credential handling:** 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.
- **Discovery method:** Agents search Jentic by intent such as 'send a templated email' or 'add a user to a list', and Jentic returns the matching Sailthru operation with its input schema for template name, recipient, and variables so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **SendGrid Mail API** — SendGrid focuses on transactional email delivery with simpler auth and a flat API surface.
- **Klaviyo API** — Klaviyo is a customer-data and email platform with deep e-commerce integrations.
- **Mailchimp Marketing API** — Mailchimp covers email marketing with a broad SMB feature set.
- **Braze API** — Braze handles cross-channel messaging that complements Sailthru's email-first focus.

## FAQ

### Why is there no official OpenAPI spec for Sailthru (Engage by Marigold) API?

Marigold does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Sailthru (Engage by Marigold) 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 Sailthru API use?

Sailthru uses an API key plus an HMAC-MD5 signature over the request payload, sent as api_key and api_sig query parameters. Through Jentic both values are computed server-side from credentials in the vault, so the agent never handles the secret or the signing logic.

### Can I send a transactional email with the Sailthru API?

Yes. POST to /send with the recipient's email, a template name, and any custom variables; Sailthru renders the template server-side using the recipient's user profile and queues the send.

### What are the rate limits for the Sailthru API?

Sailthru does not publish hard rate limits in this spec; in practice plans throttle bulk send and profile-update calls. If you receive a 429 from /send or /user, back off exponentially before retrying through Jentic.

### How do I schedule a campaign blast through Jentic?

Search Jentic for schedule a Sailthru blast, load the schema for /blast, and execute with list, subject, html_body, and schedule_time. Jentic returns the new blast id which you can poll back for status.

### Can I update user profile variables in bulk?

The /user endpoint updates a single profile per call; for bulk updates loop the call across the changeset and pace the requests. Each call accepts an arbitrary vars object so a single request can set many attributes at once.

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

Yes. Because you run Jentic One yourself, your own rules decide which Sailthru operations the agent may call, so you can allow it to send a templated email or read a list while withholding others. Sailthru's send, blast, list, and template calls carry their target in the request body rather than the URL, so a broadcast blast is only reachable if you include the blast operation in the agent's allowed set. The api_key stays with your self-hosted instance and is injected at execution time, so the agent never gains access beyond the operations you grant.