Custom metadata

Pre-recorded Live You can add metadata to your transcription using the custom_metadata property. This helps recognize your transcription when fetching results, and enables filtering via the list endpoints.

Pre-recorded: add custom_metadata to your POST request to /v2/pre-recorded, then filter via GET /v2/pre-recorded or fetch via GET /v2/pre-recorded/:id.
Live: add custom_metadata to your session configuration, then filter via the GET /v2/live list endpoint or fetch via the GET /v2/live/:id endpoint.

For example:

"custom_metadata": {
  "internalUserId": 2348739875894375,
  "paymentMethod": { "last4Digits": 4576 },
  "internalUserName": "Spencer"
}

Now, you’ll be able to filter transcription jobs based on their metadata:

https://api.gladia.io/v2/pre-recorded?custom_metadata={"internalUserId": "2348739875894375"}

https://api.gladia.io/v2/live?custom_metadata={"internalUserId": "2348739875894375"}

or:

https://api.gladia.io/v2/pre-recorded?custom_metadata={"paymentMethod": {"last4Digits": 4576}, "internalUserName": "Spencer"}

https://api.gladia.io/v2/live?custom_metadata={"paymentMethod": {"last4Digits": 4576}, "internalUserName": "Spencer"}

custom_metadata cannot be longer than 2000 characters when stringified.

Audio-to-LLM

SDK

⌘I

Introduction

Speech-to-Text

Language

Audio Intelligence

Integrations

Developer tools

Limits & Specifications

Migrations

Custom metadata