Skip to main content
Note Generation v2 is only meant for legacy customers. Its primary purpose is backward compatibility with existing systems built on Note Generation v1, while bringing newer model capabilities to those integrations. For new integrations, use Note Generation v3.
The request body, authentication, responses, polling, and webhooks remain compatible with Note Generation v1.

Migrate from Note Generation v1

Use POST /v2/notes to generate notes with Note Generation v2: For accounts enabled for Note Generation v2, GET and DELETE work across both versions. Notes created through either version can be retrieved or deleted through either version using the same noteId. Send your existing Note Generation v1 request body and X-Account-Id and X-Api-Key headers unchanged.

Lifecycle

  1. POST /v2/notes validates and accepts the job.
  2. Store the returned noteId.
  3. Poll GET /v2/notes/{noteId} until status is STATUS_DONE or STATUS_ERROR.
  4. Read the note from payload.markdown and, when requested, structured output from payload.json.
  5. Optionally delete the resource with DELETE /v2/notes/{noteId}.

TypeScript SDK

Python SDK

Create a note

Response (200):

Request fields

Poll the note

While the job is running:
When generation succeeds:
When includeJson is enabled and structured output is available, data.payload.json is a JSON object. A failed job remains retrievable with status: "STATUS_ERROR". Poll every 1–2 seconds until STATUS_DONE or STATUS_ERROR.

Delete a note

The response (200) contains data.message: "Note deleted successfully".

Errors

Error response: