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

# ActiveTrail API

Jentic publishes the only available OpenAPI specification for ActiveTrail API, keeping it validated and agent-ready. ActiveTrail is an email marketing and automation platform with endpoints for contacts, groups, email campaigns, SMS campaigns, and automations. The spec covers 20 operations under five tags - Contacts, Groups, Campaigns, Automations, and SMS - with the API key passed in the Authorization header. The base URL points at ActiveTrail's MyMarketing platform.

## For AI agents

Send email and SMS campaigns, manage contact lists, and trigger marketing automations through ActiveTrail's API.

## Scope

Does not handle deliverability infrastructure, push notifications, or paid advertising - use for ActiveTrail email and SMS campaigns, contact lists, and automation triggers only.

## Capabilities

- Manage subscribers and bulk-import contacts via /contacts and /contacts/ImportContactsBulk
- Organise audiences into groups and add or remove members through /groups and /groups/{groupId}/members
- Send and schedule email campaigns using /campaigns and /campaigns/{campaignId}/send
- Trigger SMS campaigns through the /smscampaign endpoint
- Fire marketing automations on contact events via /automations/{automationId}/trigger
- Look up and update single contacts by email at /contacts/{email}

## Use cases

### Newsletter subscriber sync

Marketers sync website signups into ActiveTrail to drive newsletter sends. An agent can POST a new contact to /contacts when a form is submitted, attach them to a group via /groups/{groupId}/members, and confirm subscription status. The bulk-import endpoint /contacts/ImportContactsBulk handles larger CSV uploads from partner lists.

Example prompt: POST a new contact to /contacts with email and first_name, then add them to group 12 via /groups/12/members

### Campaign scheduling

Email marketing teams schedule weekly newsletters and promotional sends. An agent can create a campaign at /campaigns, set its target group, and trigger send through /campaigns/{campaignId}/send. Pair this with an automation trigger so abandoned-cart or onboarding flows fire on contact events without a marketer manually clicking send.

Example prompt: Create a campaign for group 7 at /campaigns and trigger send via /campaigns/{campaignId}/send

### SMS notification flow

Retailers and event organisers send time-sensitive SMS to customers. An agent can post to /smscampaign with the audience, message body, and send time. Combined with an automation trigger, the agent can also fire an SMS when a customer enters a workflow stage.

Example prompt: POST to /smscampaign with group_id, message body, and a scheduled send time for a flash-sale alert

### AI agent integration

Marketing teams building agent assistants expose ActiveTrail through Jentic alongside CRM and analytics APIs. Through Jentic, the agent searches by intent, e.g. 'send an ActiveTrail campaign', and the API key stays in your Jentic One instance.

Example prompt: Search Jentic for 'add a contact to ActiveTrail and send a welcome campaign', load both schemas, and execute the chain

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /contacts | Add a contact |
| GET | /contacts/{email} | Look up a contact by email |
| POST | /contacts/ImportContactsBulk | Bulk import contacts |
| GET | /groups | List groups |
| POST | /groups/{groupId}/members | Add member to group |
| POST | /campaigns/{campaignId}/send | Send a campaign |
| POST | /smscampaign | Send an SMS campaign |
| POST | /automations/{automationId}/trigger | Trigger an automation |

## Key resources

- **Contacts** — Subscriber records - create, update, look up by email
- **Groups** — Audience segments and group membership
- **Campaigns** — Email campaign creation and send
- **SMS** — Bulk SMS campaign send
- **Automations** — Trigger marketing automation flows

## Why Jentic

- **Setup:** Wiring the ActiveTrail API by hand means attaching the Authorization header on every call and tracking group, campaign, and automation ids across email and SMS endpoints. Through Jentic you install once, import the ActiveTrail API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** ActiveTrail mixes body-driven creates with path-scoped sends, so limit the agent to the operations it needs, such as adding a contact or sending a campaign. You choose the operations it may call, so triggering automations or bulk importing contacts is not included unless you add them.
- **Credential handling:** Your ActiveTrail API key is stored once, encrypted, by your own Jentic One instance and injected as the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'send an ActiveTrail campaign' or 'add a contact', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mailchimp API** — Larger global email marketing platform with broader template and analytics tooling.
- **Klaviyo API** — E-commerce-focused email and SMS marketing with deep store integration.
- **Constant Contact API** — Long-standing email marketing platform popular with small businesses.

## FAQ

### Why is there no official OpenAPI spec for ActiveTrail API?

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

ActiveTrail uses an API key passed in the Authorization header. You generate the key in your ActiveTrail account settings. Through Jentic, the API key is stored encrypted in your Jentic One instance and the agent receives a scoped execution handle, never the raw key.

### Can I send email and SMS campaigns with the ActiveTrail API?

Yes. Email campaigns are created at /campaigns and triggered by POST /campaigns/{campaignId}/send. SMS campaigns go through /smscampaign with the audience and message body. Marketing automations can be triggered on demand via /automations/{automationId}/trigger.

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

The OpenAPI spec does not declare explicit rate limits, so check ActiveTrail's developer documentation for the current ceiling. Bulk loads should go through /contacts/ImportContactsBulk rather than thousands of single-contact POSTs.

### How do I add a contact and send a campaign through Jentic?

Run pip install jentic, search Jentic for 'add an ActiveTrail contact', load the POST /contacts schema, then chain a search for 'send an ActiveTrail campaign' and load /campaigns/{campaignId}/send. Jentic handles the Authorization header from the vault.

### Does the ActiveTrail API support contact lookup by email?

Yes. GET /contacts/{email} returns the contact record for a given email address - useful for checking whether someone is already subscribed before adding them or for fetching their group memberships.

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

Yes. Because Jentic One is self-hosted, you set the rules for which ActiveTrail operations your agent may call, so you can allow it to add a contact via POST /contacts or send a campaign via POST /campaigns/{campaignId}/send while leaving everything else off. Operations you do not grant, such as bulk importing through /contacts/ImportContactsBulk or firing /automations/{automationId}/trigger, stay unavailable until you add them. Your ActiveTrail API key is held by your own instance and injected only at execution, so the agent acts strictly within the scope you define.