Skip to main content
When Dolva analyzes an audio file, it returns a JSON object containing the detected signals. This page explains how to interpret the response, what the signal values mean, and how to use them in your application.

Response Structure

Both analysis endpoints (/v1/analyze/cognitive and /v1/analyze/emotion) return an application/json body on success. The top-level structure contains a status indicator and a signals object with the extracted data:
Cognitive Response Example
Emotion Response Example
The exact fields in the signals object may vary as Dolva’s models evolve. Design your integration to handle additional or missing fields gracefully — use optional chaining or null checks rather than assuming all fields are always present.

Cognitive Signals

Cognitive signals describe the speaker’s mental state as reflected in their speech patterns. Reading the scores: values closer to 1.0 indicate stronger expression of that signal. A cognitive_load of 0.8 suggests high mental effort; a value of 0.2 suggests relaxed, low-effort processing.

Emotion Signals

Emotion signals describe the affective properties of the audio.

Using Signals in Your Application

Here are practical patterns for working with the response data:
Python

Tracking Changes Over Time

Dolva’s signals are most powerful when compared across multiple recordings of the same person or conversation context. A single data point gives you a snapshot; a series of recordings reveals trends — cognitive fatigue accumulating across a workday, or emotional tone shifting across a therapy program. Store the full response JSON alongside a timestamp and a subject identifier, then compute trends in your own data layer.
Normalize signals to your own baseline before drawing conclusions. Individual speakers differ in their natural acoustic profiles — what counts as “high” cognitive load varies person to person.