Note Taker API

Turn a meeting audio recording into structured meeting notes (markdown + a DOCX). Two steps: audio → speaker dialog, then dialog → notes. New third-party feature.

Different base URL. Note Taker is served by the main app, not the translation-file host: https://www.doctranslate.io/api/v1/third-party/note-taker/… — same X-API-Key. A bad key returns 401 INVALID_API_KEY.

Step 1 — Audio → dialog

• POST /audio2dialog (multipart/form-data, field files = the meeting audio) → returns a task_id.

• Poll GET /audio2dialog/{task_id} until data.result.dialog_url is set, then fetch that URL for the JSON speaker dialog.

Step 2 — Dialog → meeting notes

• POST /dialog2meeting (send the dialog) → returns a task_id.

• Poll GET /dialog2meeting/{task_id} until data.result is set:

  • data.result.markdown — the notes as markdown

  • data.result.docx_url — a downloadable DOCX of the notes

Quick start (cURL)

BASE=https://www.doctranslate.io/api/v1/third-party/note-taker

# 1) audio -> dialog
curl -s $BASE/audio2dialog -H "X-API-Key: dtl_xxx" -F "files=@meeting.mp3"
# -> { "data": { "task_id": "A" } }
curl -s $BASE/audio2dialog/A -H "X-API-Key: dtl_xxx"
# -> { "data": { "result": { "dialog_url": "https://..." } } }

# 2) dialog -> meeting notes
curl -s $BASE/dialog2meeting -H "X-API-Key: dtl_xxx" -d @dialog.json
# -> { "data": { "task_id": "B" } }
curl -s $BASE/dialog2meeting/B -H "X-API-Key: dtl_xxx"
# -> { "data": { "result": { "markdown": "# Meeting…", "docx_url": "https://..." } } }

Notes

• Both steps are async (poll the matching GET .../{task_id}).

• Not included in the OpenAPI spec (different service) — call the base URL above directly.