The Miles API

Routes the input through Miles's intent parser and the matching handler — calendar, inbox, tasks, memory, transcripts, and more. Returns a natural-language response plus any structured data Miles surfaced.

Request body

curl -X POST https://api.heymiles.app/api/v1/ask \
  -H "Authorization: Bearer $KEY" \
  -H "Content-Type: application/json" \
  -d '{"input":"Find inbox info for my 4pm meeting"}'

{
  "intent": "meeting_prep",
  "response": "From your inbox, three threads relate to your 4pm with Sarah...",
  "data": {
    "meetings": [{ "summary": "Pricing review", "time": "4:00 PM - 4:30 PM" }],
    "emails": [{ "subject": "Re: Pricing draft", "from": "sarah@…", "snippet": "…" }]
  },
  "navigation": "/meetings/<id>/prep",
  "suggestedFollowups": ["Draft a follow-up", "What's after this meeting?"]
}

Runs the transcript through Miles's processing pipeline: rich markdown summary (lead + Overview + sectioned notes), action items with priorities, decisions with reasoning, topics, attendees, and a drafted follow-up email. Side-effect: creates Tasks and Action records in the user's app.

curl -X POST https://api.heymiles.app/api/v1/transcripts \
  -H "Authorization: Bearer $KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "meetingTitle": "Vectris Q2 sync",
    "meetingDate": "2026-05-09T14:00:00Z",
    "attendees": ["Bill Barry", "Vicki Chen"],
    "rawTranscript": "Speaker 1: Lets review pricing..."
  }'

Response

{
  "transcriptId": "clx…",
  "summary": "Bill and Vicki aligned on Q2…\n\n**Overview**\n- …",
  "actionItems": [{ "title": "Send pricing deck by EOD Friday", "priority": "immediate" }],
  "decisions": [{ "topic": "Pricing model", "decision": "Per-seat for Q2" }],
  "topics": ["pricing", "Q2 launch"],
  "tasksCreated": 3,
  "memoryRecords": 5,
  "followUpDrafted": true
}

List the Recall.ai bot recordings available for grabbing. Each record carries a botId (use it directly with /transcripts/grab for the cheapest match), meeting title/date, current status, and whether it's already been processed.

Pull a transcript from a Recall.ai bot recording (Miles' own bot) and run it through the processing pipeline. Equivalent to the in-app "Grab Transcript" button, exposed for automation. Either pass botId directly (best) or any of meetingTitle, meetingDate, meetingId and Miles fuzzy-matches a recording.

{ "botId": "abc123" }
// — or —
{ "meetingTitle": "Q2 Pricing Call", "meetingDate": "2026-05-09T14:00:00Z" }

Response status values

The single most recent processed meeting with full detail. Powers "what was my last meeting about?" use cases without needing to list-then-fetch.

curl https://api.heymiles.app/api/v1/meetings/last \
  -H "Authorization: Bearer $KEY"

List processed meetings, most-recent-first. range is past (default) or today. Returns brief previews + counts.

Full detail for one meeting: rich markdown summary, raw transcript, actionItems, decisions, topics, followUpDraft.

Remove a meeting and its derived records (action items, decisions, follow-up draft, memory entries). Returns { deleted: true }.

Delete up to 200 meetings in one call. Body: { "ids": [...] }. Returns { deleted, errors, requested }.

Create or update a contact. Upserts by (userId, email). Email is optional when name or company is present. tags are trimmed + lowercased (max 20) and merged with existing tags by default — send "tagsMode": "replace" to make your payload authoritative. Every response includes tags: string[].

{
  "name": "Sarah Chen",
  "email": "sarah@weka.vc",
  "company": "Weka Ventures",
  "title": "Partner",
  "notes": "Met at Demo Day. Lead on early-stage.",
  "tags": ["investor", "warm"],
  "tagsMode": "merge"
}

Sync up to 100 contacts in one call — each may carry its own tags; a request-level tagsMode applies to the batch. Returns { created, updated, skipped, errors, total }. Perfect for "new row in Sheets → push to Miles" Zapier flows.

{ "contacts": [
  { "name": "Sarah Chen", "email": "sarah@weka.vc", "tags": ["investor"] },
  { "name": "Bill Barry", "email": "bill@modius.com", "title": "CEO", "tags": ["ais6", "speaker"] }
]}

Paginated search. q matches across name / email / company / notes. tag=investor,warm returns contacts carrying all listed tags.

Every tag in use, with contact counts: { tags: [{ tag, count }], count }.

Fetch one contact by id.

Add tags to a contact (idempotent). Body { "tags": ["speaker"] }. Use PUT on the same path to replace the whole set ([] clears), and DELETE /api/v1/contacts/:id/tags/:tag to remove one. All return the updated contact.

Create a task. Required: title. Validated horizon: right_now | short_term | horizon. Validated status: pending | in_progress | completed | cancelled.

{
  "title": "Send pricing proposal to Sarah",
  "horizon": "right_now",
  "dueDate": "2026-05-12",
  "description": "Per the Vectris call — needs the per-seat tier laid out."
}

List tasks. Filter by horizon and/or status.

Upsert a memory by (userId, key). Required: category, key, value.

{
  "category": "preference",
  "key": "preferred_meeting_time",
  "value": "Mornings before 11am"
}

Search memory. q matches across key and value.

Delete a memory entry by id.

Every decision Miles has captured. Each has topic, decision, context, and the source meeting.

Lists every sprint (active / planned / completed) with task and done counts.

Full detail with stages and tasks. Each task carries stageId, stageName, status, priority, blocked reason, due date, primary assignee, full assignees roster, category, externalId, and updatedAt. Read stage ids here before writing — stages are addressed by id (names aren't unique).

Create a card. Defaults to the first stage. Assign by assigneeIds, assigneeEmails (team members only), and/or assigneeAgentIds. Give it an externalId (your CRM row / sheet id — unique per sprint) and a retried create updates that card instead of duplicating it (200 instead of 201). status is derived from the stage. category is an optional free-text board label (max 40 chars) — the in-app board can be filtered down to one category.

{
  "title": "Draft AIS6 sponsor deck",
  "stageId": "3f1c…",
  "priority": "high",
  "dueDate": "2026-09-01",
  "assigneeEmails": ["troy@ignitegtm.com"],
  "category": "Finance",
  "externalId": "crm-42"
}

Edit, move, or reassign a card. Any of title, description, stageId, priority, dueDate, blockedReason, category, externalId, assignee keys (sending any assignee key replaces the whole roster; [] unassigns). Moving to a Done-type stage sets status: "done" + completedAt. Add ifUpdatedAt (the card's last updatedAt) to make the write conditional — you get 409 conflict with the card's current state if someone moved it first. DELETE on the same path removes the card.

Update a whole board in one request: up to 100 ordered create / update / delete operations, each with exactly the granular body above. Give a create a ref and later ops can address that card as "$ref". By default each op commits on its own and failures are isolated per item; "atomic": true makes it all-or-nothing (a failure returns 409 batch_rolled_back with the failing index and cause); "dryRun": true validates everything — refs, stages, assignees, ids — and writes nothing. A malformed op fails the whole batch with 400 + index before anything runs. Only real stage moves emit sprint.stage_changed / task.completed webhooks, after commit. For CSV / CRM sync: put an externalId on every create and re-run the same batch freely — it converges instead of duplicating.

{
  "operations": [
    { "op": "create", "ref": "row-1", "data": { "title": "Book venue", "externalId": "sheet-1" } },
    { "op": "update", "taskId": "$row-1", "data": { "stageId": "<in-progress-stage-id>" } },
    { "op": "update", "taskId": "8f0c…", "data": { "priority": "critical" } },
    { "op": "delete", "taskId": "2b1e…" }
  ],
  "atomic": false,
  "dryRun": false
}

{
  "results": [
    { "index": 0, "op": "create", "ref": "row-1", "ok": true, "created": true, "task": { … } },
    { "index": 1, "op": "update", "taskId": "…", "ok": true, "task": { … } },
    { "index": 3, "op": "delete", "taskId": "…", "ok": false, "error": { "code": "not_found", "message": "Task not found" } }
  ],
  "succeeded": 3, "failed": 1, "total": 4, "atomic": false
}

Copy an existing Miles Action or Task onto the board as a card. Body { "source": "action" | "task", "sourceId", "stageId"? }. Preserves the assignee (human or agent).

Runs a Gmail query against the user's full inbox (no time window). Returns matched threads. Auto-prefixes in:inbox, falls back to recent emails when nothing matches.

Returns 412 if the user hasn't connected Gmail. For an AI-summarized answer instead of raw threads, use /v1/ask.

{ "query": "from:sarah pricing", "limit": 15 }

Generates a fresh daily briefing via Claude. Returns the structured briefing (greeting, narrative, attentionItems, suggestedActions) plus the events / emails / pending actions it was composed from.

Activity log feed. Common action values: briefing_generated, transcript_processed, task_created, email_sent, meeting_prepped, action_executed.