canonical: https://jentic.com/apis/encharge.io/encharge # Encharge API Jentic publishes the only available OpenAPI specification for Encharge API, keeping it validated and agent-ready. Encharge is a marketing automation platform built around people (contacts), tags, events, and broadcast and transactional emails. The API exposes the operations needed to create or update people, tag them for segmentation, track behavioural events that drive flows, and send transactional emails. Use it to wire product activity directly into nurture sequences without writing custom integration glue. ## For AI agents Create and update people, tag for segmentation, track events that drive flows, and send transactional emails through Encharge. ## Scope Does not handle CRM deal pipelines, SMS, or ad campaign management - use for SaaS marketing automation and transactional email only. ## Capabilities - Create or update a person record by email to keep the contact graph in sync - Add or remove tags on a person to drive segmentation and flow entry - Track product or behavioural events that fire automation flows - Send a transactional email triggered by application logic - Look up a person by email to read their current state before updating - Delete a person to honour data subject deletion requests ## Use cases ### Product Event-Driven Nurture Wire product activity into Encharge so behavioural events drive automation flows automatically. The API exposes POST /events for tracking and POST /people for upserts so the contact and event graph stays current as users interact with the product. Marketing operations teams use this to replace generic time-based campaigns with flows that fire on real product behaviour. Example prompt: POST /people to upsert the contact, then POST /events with the event name and properties to fire the matching flow. ### Lifecycle Tagging Tag contacts as their lifecycle changes - trial started, paid, churned - so segmentation in Encharge stays in sync with the source of truth in product or billing systems. The API exposes POST /tags and DELETE /tags for managing tag membership per person. Lifecycle marketing teams use this to keep audience segmentation reliable without manual list uploads. Example prompt: POST /tags with {tag, email} to add the tag, and DELETE /tags with the same payload to remove a stale tag. ### Transactional Email from Application Code Send transactional emails - receipts, password resets, in-app notifications - through Encharge so transactional and marketing email share the same template and tracking layer. The API exposes POST `/emails/send` with the recipient and template payload. Engineering teams use this to consolidate sender domains and reporting across both email types. Example prompt: POST `/emails/send` with the recipient email, template identifier, and merge variables for the message. ### Agent-Driven Lifecycle Sync An agent watching billing webhooks updates the matching Encharge contact, tags lifecycle status, and tracks the event so the right nurture flow fires. Through Jentic the agent searches by intent, loads the schemas, and chains calls without bespoke client code. The lifecycle sync that previously required custom middleware drops to a single agent task. Example prompt: Search Jentic for 'update a marketing automation contact', execute POST /people, POST /tags, and POST /events for the lifecycle event in sequence. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/people` | Create or update a person | | GET | `/people/{email}` | Get a person by email | | DELETE | `/people/{email}` | Delete a person | | POST | `/tags` | Add a tag to a person | | DELETE | `/tags` | Remove a tag from a person | | POST | `/events` | Track an event for a person | | POST | `/emails/send` | Send a transactional email | ## Key resources - **People** — Upsert, retrieve, and delete contact records by email - **Tags** — Add and remove tags on a person for segmentation - **Events** — Track behavioural events that drive automation flows - **Emails** — Send transactional emails to a person ## Why Jentic - **Setup:** Wiring the Encharge API by hand means setting up its X-Encharge-Token header, formatting people, tag, event, and email calls, and handling your own retries against https://api.encharge.io/v1. Through Jentic you install once, import the Encharge API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** The Encharge API puts the person's email in the URL path (`/people/{email}`), so a rule can pin your agent to one person: it can read that person and nothing else. You choose the operations it may call, so ones like deleting a person or sending transactional email are not included unless you add them. - **Credential handling:** Your Encharge token 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 a person to Encharge' or 'send a transactional email', and Jentic returns the matching Encharge operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Customer.io Track API** — Behavioural marketing automation with similar people-and-events model - **Klaviyo API** — E-commerce-led marketing automation platform - **Brevo API** — Marketing platform with broader email and SMS features - **Kit (ConvertKit) API** — Creator-focused email automation ## FAQ ### Why is there no official OpenAPI spec for Encharge API? Encharge does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Encharge 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 Encharge API use? The API uses an API key passed in the X-Encharge-Token header. Through Jentic the token is held encrypted in the vault and injected into the header at execution time, so it never enters an agent's context. ### Can I track a product event with the Encharge API? Yes. POST /events accepts the event name, the person's email, and a properties object. Encharge uses the event to fire any matching automation flows. ### How do I send a transactional email through Jentic? Search Jentic for 'send a transactional email Encharge', load the schema for POST `/emails/send`, and execute it with the recipient and template variables. ### What are the rate limits for the Encharge API? The OpenAPI spec does not declare quantitative rate limits. Encharge enforces limits at the account level; treat HTTP 429 responses as authoritative and respect any Retry-After header. ### Can I delete a person from Encharge for GDPR compliance? Yes. DELETE `/people/{email}` removes the person record so subsequent calls referencing that email return 404. Use this path for data subject deletion requests. ### Can I limit what my agent is allowed to do with the Encharge API? Yes. Because you run Jentic One yourself, your own rules decide which Encharge operations and credentials the agent can use. Since the person's email sits in the URL path at `/people/{email}`, a rule can pin the agent to a single person so it reads that record and nothing else. You also choose the operations it may call, so higher-impact ones like DELETE `/people/{email}` or POST `/emails/send` stay off unless you add them.