canonical: https://jentic.com/apis/missiveapp.com/missive # Missiveapp Missive API Jentic publishes the only available OpenAPI specification for Missive API, keeping it validated and agent-ready. Missive is a team inbox and collaboration platform for email, SMS, and chat. The public API exposes endpoints to create draft emails, sync contacts, and read shared conversations across the team. Useful when an automation needs to draft outreach in Missive for human review or pull conversation threads into other tools. ## For AI agents Create email drafts in a shared Missive inbox, sync contacts, and read conversation threads through the public Missive API. ## Scope Does not handle outbound SMS, calendar scheduling, or full ticketing workflows - use for shared inbox drafts, contacts, and conversation reads only. ## Capabilities - Create a new email draft in a shared inbox via POST /drafts with recipients, subject, and body - Create or update a contact record using POST /contacts so it appears in the team's address book - Retrieve a single conversation by id via GET `/conversations/{id}` including its messages and metadata - List conversations with GET /conversations to surface threads matching the team's filters ## Use cases ### AI-Drafted Replies for Human Review An agent reads incoming customer messages from a shared inbox, drafts a reply, and posts it as a Missive draft via POST /drafts so a human teammate can review, edit, and send. Captures the speed of automation without sending unreviewed copy to customers. Example prompt: POST /drafts to the shared inbox with the recipient, subject, and AI-drafted body, leaving the message unsent for human review ### Contact Sync from External Systems Push contact records from a CRM or signup form into Missive via POST /contacts so teammates see context the moment a thread arrives. The endpoint handles both creation and updates so nightly sync jobs stay simple. Example prompt: POST /contacts with email, name, and phone for every new lead added in the CRM in the last 24 hours ### Conversation Export for Analysis Pull conversation threads with GET `/conversations/{id}` into a data warehouse or analytics tool to analyse response times, sentiment, or topic mix. Use GET /conversations to discover ids matching the desired filter, then fetch each thread's full message history. Example prompt: GET /conversations to list ids, then GET `/conversations/{id}` for each to extract messages into a warehouse table ### Agent-Driven Inbox Workflows An AI agent uses Jentic to orchestrate Missive: read inbound threads, draft suggested replies, sync contacts. The bearer token sits in your Jentic One instance, scoped to the team's account, so the agent never holds the secret directly. Example prompt: Search Jentic for 'create a draft email', load the Missive draft schema, and post drafts for every unanswered customer thread from today ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/drafts` | Create an email draft | | POST | `/contacts` | Create or sync a contact | | GET | `/conversations` | List conversations | | GET | `/conversations/{id}` | Get a conversation by id | ## Key resources - **Drafts** — Create email drafts in shared Missive inboxes - **Contacts** — Create or sync contacts visible to the whole team - **Conversations** — List and retrieve full conversation threads ## Why Jentic - **Setup:** Wiring Missive by hand means handling its bearer auth against public.missiveapp.com and coding the draft, contact, and conversation calls yourself. Through Jentic you install once, import Missive from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Missive puts the conversation id in the URL path (`/conversations/{id}`) for reads, while drafts and contacts carry their content in the request body, so scope the agent to the operations it needs, such as reading a conversation or creating a draft. You choose which operations are allowed, so creating a contact is only included if you add it. - **Credential handling:** Your Missive bearer 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 'create a draft email' or 'read a conversation', and Jentic returns the matching Missive operation with its input schema so the agent calls the right endpoint without a separate Missive docs lookup. ## Related APIs - **Help Scout** — Help Scout is a help desk platform with shared inboxes and customer profiles - **Intercom** — Intercom handles in-product chat that can route conversations into Missive when escalated ## FAQ ### Why is there no official OpenAPI spec for Missive API? Missive does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Missive 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 Missive API use? Missive uses HTTP bearer token authentication. The token is sent in the Authorization header as `Bearer ` and can be issued from the Missive integrations settings. Jentic stores the token in its vault and injects it per call. ### Can I create a draft email with the Missive API? Yes. POST /drafts creates an unsent draft in a shared inbox. Provide the recipients, subject, and body; teammates will see the draft alongside other inbox items and can edit or send it. ### How do I retrieve the full message history for a conversation? Call GET `/conversations/{id}` with the conversation id. The response includes the conversation metadata and the ordered list of messages on the thread, including authors and timestamps. ### How do I draft customer replies through Jentic? Run `pip install jentic`, search Jentic for 'create a draft email', and Jentic returns the Missive POST /drafts operation. Provide the inbox, recipients, subject, and AI-generated body, then execute. The draft appears in Missive for human review. ### Can I limit what my agent is allowed to do with the Missive API? Yes. Because you run Jentic One yourself, your own rules decide which Missive operations the agent may call and which bearer token it uses. You can allow only reads, such as GET /conversations and GET `/conversations/{id}`, or add write operations like POST /drafts and POST /contacts one at a time, so creating a contact is available only if you include it. The token stays in your own instance and is injected at execution, so the agent never handles the secret directly.