Italic

A recording is an audio input. The app transforms it into one of two types:

Clip (clip) — a short burst, command, or quick note. Only text is saved; the audio is deleted immediately after conversion to text.
Memo (memo) — a longer recording or note. Both text and audio are saved, with the audio kept locally.

Text syncs to the cloud. Memo audio stays on the client that holds it; the API can reference local file IDs without storing the audio. “Recording” is the shared input and API resource, not a third type or another name for Memo. The app’s selected input mapping determines the result, not the firmware or a duration threshold. Base URL: https://app.italic.com/api/v2.

Create your first recording

Create an API key in Settings → API & integrations. Select recordings:create and recordings:read to follow this example.

curl https://app.italic.com/api/v2/recordings \
  -H "Authorization: Bearer $ITALIC_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: meeting-123' \
  --data '{"type":"memo","title":"Planning","transcript":"Discuss the next release."}'

Only type is required in the body. Italic supplies an ID and timestamp. Reuse the same retry key and body if a request fails or its response is lost. Read a recording with GET /recordings/{id}, edit selected fields with PATCH /recordings/{id}, or search the library with GET /recordings.

Next steps

Recordings: the object, editing, search, and optional local audio references.
Device settings: choose what each recording input creates.
Webhooks: receive recording notifications.
MCP: connect an assistant to your library.

Download the OpenAPI document to generate a client. Existing app clients and v1 integrations continue working; see compatibility.

Start here

Integrations

Create your first recording

Next steps

​Create your first recording

​Next steps

Create your first recording

Next steps