Skip to main content
POST
Create a recording to represent a captured conversation. After creation, use the upload endpoints to upload the audio file.

Authentication

This endpoint behaves differently depending on your authentication method: Using API Keys:
  • Required: device_id and end_user_id in request body
  • Use case: Mobile apps uploading on behalf of users via Bluetooth sync
Using Device Tokens:
  • Required: Neither device_id nor end_user_id (automatically extracted from token)
  • Use case: 4G/WiFi devices uploading directly to the cloud
See the examples below for both scenarios.

Request Body

device_id
string
ID of the device that captured (or will capture) the recording. Optional for API-uploaded audio files.Note: When using device tokens (dtok_*), this field is automatically populated from the token and should NOT be included in the request.
end_user_id
string
ID of the end user. Required when using API keys.Note: When using device tokens (dtok_*), this field is automatically populated from the token and should NOT be included in the request.
name
string
Optional human-readable name for the recording (e.g., “Weekly standup”, “Client call with Acme”).
started_at
string
ISO 8601 timestamp of when the recording started (device time).
ended_at
string
ISO 8601 timestamp of when the recording ended (device time).
metadata
object
Arbitrary key-value metadata (e.g., meeting type, location).

Response

Returns the created recording object.

Response Fields

Recording Status

Next Steps

After creating a recording:
  1. Get an upload URL
  2. Upload audio to the pre-signed S3 URL
  3. Mark upload complete
  4. Trigger transcription