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

# Itsconvo Convo API

The Convo API gives your code the sales calls the Convo desktop app records: transcripts, key points, coaching feedback, and answers to questions about a single call. It drafts follow-up emails in a professional, casual, or concise tone, shares a call by link, renames or deletes it, and lists upcoming events from the connected Google or Outlook calendar. On Professional and Enterprise plans, Convo Memory adds contact lists, open action items from past meetings, and pre-call briefings, and webhooks report events such as transcript.ready and conversation.feedback.ready.

## For AI agents

Read recorded sales-call transcripts and key points from Convo, ask questions about a call, generate coaching feedback and follow-up emails, and pull contact briefings and open action items before the next meeting.

## Scope

Does not record calls itself, send emails, or manage CRM deals. Use for reading and acting on calls recorded by the Convo desktop app only.

## Capabilities

- Search recorded calls by title or transcript words and read a call's transcript oldest segment first
- Generate or read the key points and coaching feedback for a call, with forceRefresh to regenerate them
- Ask a question about one call and get an answer drawn from its transcript
- Draft a follow-up email from a call for a recipientName in a professional, casual, or concise tone
- Pull a Convo Memory briefing on a contact with relationship summary, recent meetings, open action items, and decisions
- Register HTTPS webhooks for events such as transcript.ready and conversation.keypoints.ready, and send a signed test event

## Use cases

### Agent-drafted call follow-ups

An AI agent acting as a sales assistant turns each recorded call into a follow-up without the rep copying notes. Through Jentic the agent searches for 'draft a follow-up email from a call', finds the latest conversation, reads its key points, and asks Convo to draft the email for the named recipient, with the convo_ key injected at call time. Each email draft uses one AI credit, so the agent only drafts for calls that need a reply.

Example prompt: Call GET `/api/v1/conversations` with limit 1, then POST `/api/v1/conversations/{id}/keypoints` and POST `/api/v1/conversations/{id}/email` with recipientName Sarah and tone concise for that call

### Pre-call briefing

Before a meeting, a rep wants to know what was said last time and what is still open. Convo Memory returns a briefing on one contact with the relationship summary, recent meetings, open action items, and recent decisions, and the unresolved-threads read lists open action items across contacts, oldest meeting first. Both need a Professional or Enterprise plan with Memory enabled.

Example prompt: Call GET `/api/v1/calendar/events` with maxResults 5, match the next attendee in GET `/api/v1/contacts` with search, and call GET `/api/v1/contacts/{id}/briefing` for that contact

### Sales coaching review

A sales manager reviewing a rep's week reads coaching feedback on each call and asks targeted questions about objections. Feedback generation uses one AI credit and needs at least 10 transcript segments, and the query operation answers a question from one call's transcript with suggested follow-up questions.

Example prompt: Call POST `/api/v1/conversations/{id}/feedback` for a call, then POST `/api/v1/conversations/{id}/query` with query What objections did the prospect raise?

### Pushing call events into other tools

A team syncing calls into its CRM registers a webhook so new transcripts arrive without polling. Webhooks take an HTTPS url and a list of events such as transcript.ready or conversation.action_items.ready, the secret is returned once at creation, and the test operation sends a signed webhook.test event and reports the receiving server's status code.

Example prompt: Call POST `/api/v1/webhooks` with url https://hooks.example.com/convo and events transcript.ready and conversation.keypoints.ready, then POST `/api/v1/webhooks/test` with the returned webhookId

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/v1/conversations` | List and search conversations |
| GET | `/api/v1/conversations/{id}/transcript` | Get a transcript |
| POST | `/api/v1/conversations/{id}/keypoints` | Generate key points |
| POST | `/api/v1/conversations/{id}/query` | Ask a question about a call |
| POST | `/api/v1/conversations/{id}/email` | Draft a follow-up email |
| GET | `/api/v1/contacts/{id}/briefing` | Get a contact briefing |
| POST | `/api/v1/webhooks` | Register a webhook |

## Key resources

- **Conversations** — List and search calls, read transcripts, generate key points, feedback, answers, and follow-up emails, share, rename, and delete
- **Calendar** — Upcoming events from the connected Google or Outlook calendar
- **Contacts (Convo Memory)** — Contacts, unresolved threads, and per-contact briefings
- **Webhooks** — List, register, delete, and test event webhooks
- **User** — Profile, plan, and AI credits used this month

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 69 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 90 / 100
  - Developer Experience & Jentic Compatibility: 68 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 79 / 100
- **View full report:** https://jentic.com/apis/itsconvo.com/itsconvo/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Convo by hand means creating a convo_ key in the desktop app, sending it as a bearer token, and handling hourly 429 limits and plan-gated routes like webhooks and Convo Memory. Through Jentic you install once, import Convo from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Convo puts the conversation id in the URL path (`/api/v1/conversations/{id}/...`), so a rule can scope your agent to one call. You choose the operations it may call, so actions like DELETE `/api/v1/conversations/{id}` or sharing a call by link are not included unless you add them.
- **Credential handling:** Your Convo API key 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 'get a sales call transcript' or 'draft a follow-up email', and Jentic returns the matching Convo operation with its input schema so the agent calls the right endpoint.

## Related APIs

- **Gong** — Revenue intelligence platform with recorded calls, transcripts, and deal data
- **Fireflies.ai** — Meeting notetaker with transcripts and summaries
- **Pipedrive** — Sales CRM to log the outcomes of calls Convo records

## FAQ

### What authentication does the Convo API use?

Per its OpenAPI spec, every operation takes a bearer token: Authorization: Bearer with a convo_ key created in the Convo desktop app under Settings, Convo API. Keys work on Starter, Professional, and Enterprise plans. Through Jentic the key is stored by your own instance and attached at call time, so the agent never sees it.

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

The spec lists hourly limits by plan: 100 requests per hour on Starter, 500 on Professional, and 2,000 on Enterprise. Over the limit you get 429 rate_limited with Retry-After, and successful responses carry X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset. See https://docs.itsconvo.com/tiers for plan details.

### Which Convo API calls use AI credits?

Per the spec, generating coaching feedback, querying a call, and drafting a follow-up email each use one AI credit, while generating key points does not. GET `/api/v1/user/profile` returns how many AI credits you have used this month.

### Is there a Convo MCP server?

You don't need an MCP server to give your agent Convo. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the conversation, contact, and webhook operations it needs without loading another server's tool definitions into its context.

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

Yes. For example, write a rule that allows only the transcript and keypoints reads under `/api/v1/conversations/{id}`/ plus the conversation list, and the agent can read your calls but cannot share them by link, rename them, or delete them. Every call it makes is logged.

### How do I get a call transcript through Jentic?

Search Jentic for 'get a sales call transcript', load GET `/api/v1/conversations` to find the call by search term, then load GET `/api/v1/conversations/{id}/transcript` and execute it with that call's id. To run it on your own infrastructure, install Jentic One from its GitHub repo.