MindMe Account API

Name: MindMe Account API API
Brand: MindMe Account API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing AutomationapiKey7 EndpointsREST

For Agents

Manage contacts, contact types, and automation sequences, and create marketing campaigns through MindMe's account API. Suited to lightweight outreach automation.

Connect the MindMe Account API to your agent

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

Search the contact database with GET /api/Contact/Search using name, phone, or email filters

Add new contacts to the account through POST /api/Contact/AddContact

Define contact taxonomies with POST /api/Contact/CreateType and read them via GET /api/Contact/GetTypes

Launch a marketing campaign with POST /api/Campaign/Create

GET STARTED

Start building with MindMe Account API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for MindMe Account API, keeping it validated and agent-ready. MindMe is a contact and campaign automation platform that lets teams manage contacts, contact types, automation sequences, and outbound campaigns from a single account API. The seven endpoints cover the core flows: search and add contacts, define contact taxonomies, list automation sequences, and launch campaigns. Designed for small teams running multi-channel outreach without a heavy CRM.

Use Cases

Patterns agents use MindMe Account API API for, with concrete tasks.

★ Inbound Lead Capture

Add contacts from website forms or chat into MindMe and tag them with the relevant contact type so they enter the right automation sequence. The agent posts the contact, fetches the available types, and assigns one in a single short flow. Reduces the time between form submission and first marketing touch.

POST /api/Contact/AddContact with name, email, phone, and contact_type_id, then return the new contact id

Campaign Launch from a Segment

Trigger a one-shot marketing campaign by creating a campaign object scoped to a contact type. MindMe then handles delivery to all contacts under that taxonomy. Good for product announcements and time-bound promotions where the audience is already segmented in MindMe.

POST /api/Campaign/Create with name, contact_type_id, and message body to launch a campaign to all contacts of that type

Contact Database Hygiene

Search for stale or duplicate contacts and remove them with DELETE /api/Contact/Delete to keep automation sequences efficient. The search endpoint returns all matching records so the agent can apply rules — for example, deleting contacts that have not engaged in 12 months.

Use GET /api/Contact/Search to find duplicates by email, then DELETE /api/Contact/Delete on the older record id

Agent-Driven Outreach Automation

An AI agent registers new leads in MindMe through Jentic, looks up the right automation sequence, and launches a follow-up campaign. The MindMe API key sits in the Jentic vault, so the agent can act on behalf of the account without holding the secret directly.

Search Jentic for 'add a marketing contact', load the MindMe AddContact schema, and add five new contacts captured from today's webform submissions

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/api/Contact/Search

Search contacts

POST

/api/Contact/AddContact

Add a contact

DELETE

/api/Contact/Delete

Delete a contact

GET

/api/Contact/GetTypes

List contact types

POST

/api/Campaign/Create

Create a campaign

GET

/api/AutomationSequence/Sequences

List automation sequences

GET

/api/Contact/Search

Search contacts

POST

/api/Contact/AddContact

Add a contact

DELETE

/api/Contact/Delete

Delete a contact

GET

/api/Contact/GetTypes

List contact types

POST

/api/Campaign/Create

Create a campaign

GET

Why though Jentic?

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

Credential isolation

The MindMe API key is held encrypted in the Jentic vault and injected into the `Authorization` header at execution time. The agent never sees or logs the raw key, and rotation happens once in Jentic for all agents.

Intent-based discovery

Agents search Jentic by intent (e.g. 'add a contact', 'launch a campaign') and Jentic returns the matching MindMe operation with its input schema, so the agent does not need to learn the path naming convention.

Time to first call

Direct MindMe integration: roughly half a day to wire the API key, types, and campaign launch flow. Through Jentic: under 30 minutes.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Mailchimp

Mailchimp offers a broader marketing automation suite with email, audiences, and templates

Choose Mailchimp when email is the primary channel and richer audience segmentation is needed

Alternative

Brevo

Brevo combines transactional email, SMS, and marketing automation in a single API

Choose Brevo when multi-channel campaigns across email and SMS are required from one provider

Complementary

HubSpot

HubSpot stores deeper CRM context that can flow into MindMe contact records

Use HubSpot upstream as system of record and MindMe downstream for lightweight campaign delivery

FAQs

Specific to using MindMe Account API API through Jentic.

Why is there no official OpenAPI spec for MindMe Account API?

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

MindMe uses an API key in the `Authorization` request header (apiKey scheme). Through Jentic the key is stored in the vault, so agents call MindMe via Jentic execution requests without ever holding the raw key.

Can I add and tag contacts with the MindMe Account API?

Yes. POST /api/Contact/AddContact creates the contact and accepts a contact type id so the record is tagged on creation. Use GET /api/Contact/GetTypes first to retrieve the valid type ids on the account.

How do I launch a campaign through Jentic?

Run `pip install jentic`, search Jentic for 'launch a marketing campaign', and Jentic returns the MindMe POST /api/Campaign/Create operation. Provide a name, the target contact_type_id, and the message body to start delivery.

Can I see which automation sequences exist on my account?

Yes. GET /api/AutomationSequence/Sequences returns the full list of sequences configured in MindMe so the agent can choose the right one for a given contact segment before adding records.