canonical: https://jentic.com/apis/mindmemobile.com/mindme

# Mindmemobile MindMe Account API

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.

## For AI agents

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

## Scope

Does not handle email template design, A/B testing, or detailed campaign analytics - use for contact management and basic campaign launch only.

## Capabilities

- 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`
- List the automation sequences configured on the account with GET `/api/AutomationSequence/Sequences`
- Remove a contact via DELETE `/api/Contact/Delete` when records are merged or unsubscribed

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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 your Jentic One instance, so the agent can act on behalf of the account without holding the secret directly.

Example prompt: 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

| 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 |

## Key resources

- **Contacts** — Search, add, and delete contact records and define contact types
- **Campaigns** — Create marketing campaigns scoped to a contact type
- **Automation Sequences** — List the automation sequences configured on the account

## Why Jentic

- **Setup:** Wiring MindMe by hand means handling its API key in the Authorization header against api.mindmemobile.com and coding the contact and campaign calls yourself. Through Jentic you install once, import MindMe from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** MindMe's contact and campaign endpoints carry their target in the request body or query rather than a URL path resource, so scope the agent to the operations it needs, such as searching or adding a contact. You choose which operations are allowed, so deleting a contact is only included if you add it.
- **Credential handling:** Your MindMe API key is stored once, encrypted, by your own Jentic One instance and injected into 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 'add a contact' or 'launch a campaign', and Jentic returns the matching MindMe operation with its input schema so the agent calls the right endpoint without learning the path naming convention.

## Related APIs

- **Mailchimp** — Mailchimp offers a broader marketing automation suite with email, audiences, and templates
- **Brevo** — Brevo combines transactional email, SMS, and marketing automation in a single API
- **HubSpot** — HubSpot stores deeper CRM context that can flow into MindMe contact records

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

### 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.

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

Yes. Because you run Jentic One yourself, you decide which MindMe operations your agent may call, so you can allow only the ones it needs, such as GET `/api/Contact/Search` and POST `/api/Contact/AddContact`, while leaving out DELETE `/api/Contact/Delete` or POST `/api/Campaign/Create.` MindMe's endpoints pass their target in the request body or query rather than a URL path, so this operation-level allow-list is how you constrain the agent's reach. Your API key stays inside your own instance and is injected only for the operations you have permitted.
