UntangledAPI
Extract

Meeting Notes

Extract attendees, agenda, decisions, and action items from meeting notes.

POST /v1/extract/meeting-notes is built for the unstructured-but-conventional shape of typed meeting notes — header with attendees and date, free-form discussion, decisions, and action items at the end.

Request

curl https://api.untangledapi.com/v1/extract/meeting-notes \
  -H "x-api-key: $UNTANGLED_KEY" \
  -H "content-type: application/json" \
  -d '{
    "document": { "text": "<<meeting notes text>>" }
  }'

Response

{
  "data": {
    "title": "Q2 Planning",
    "meeting_date": "2026-04-15T14:00:00",
    "attendees": [
      { "name": "Alice Chen", "email": "alice@acme.com" },
      { "name": "Bob Patel" }
    ],
    "agenda": [
      "Review Q1 results",
      "Set Q2 OKRs",
      "Hiring plan"
    ],
    "decisions": [
      "Ship v0.2 by 2026-06-15",
      "Pause US-east region launch"
    ],
    "action_items": [
      {
        "task": "Draft v0.2 RFC",
        "owner": "Alice Chen",
        "due_date": "2026-04-22"
      },
      {
        "task": "Get hiring approval from finance",
        "owner": "Bob Patel",
        "due_date": null
      }
    ]
  },
  "model": "claude-haiku-4-5",
  "usage": {
    "inputTokens": 980,
    "outputTokens": 210
  }
}

Fields

FieldTypeNotes
titlestring | null
meeting_datestring (ISO 8601) | nullIncludes time if present.
attendees[]array{ name, email? }. Email surfaced when written explicitly.
agenda[] / decisions[]array of stringsEmpty array if not detected.
action_items[]array{ task, owner?, due_date? }. Owner is best-effort match against the attendee list.

What's not extracted

Free-form discussion text is intentionally not surfaced — there's no faithful schema for prose. If you need the prose body, store the source text yourself and use this endpoint only for the structured tail.

On this page