Recordings
Create Recording
Create a new recording
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_idandend_user_idin request body - Use case: Mobile apps uploading on behalf of users via Bluetooth sync
- Required: Neither
device_idnorend_user_id(automatically extracted from token) - Use case: 4G/WiFi devices uploading directly to the cloud
Request Body
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.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.Optional human-readable name for the recording (e.g., “Weekly standup”, “Client call with Acme”).
ISO 8601 timestamp of when the recording started (device time).
ISO 8601 timestamp of when the recording ended (device time).
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:- Get an upload URL
- Upload audio to the pre-signed S3 URL
- Mark upload complete
- Trigger transcription

