Transcription feedback

Attach a thumbs-up or thumbs-down to an enterprise dictation.

Every batch dictation response includes an id. Keep that value with the result so your product can submit feedback for the exact dictation.

Submit feedback

Send feedback to:

POST https://go.monologue.to/v1/enterprise/transcriptions/{transcription_id}/feedback

Use the same enterprise authentication as the dictation request and send multipart/form-data.

Thumb-only feedback is valid and is the recommended default:

curl --request POST \
  --url https://go.monologue.to/v1/enterprise/transcriptions/TRANSCRIPTION_ID/feedback \
  --header "X-API-Key: $MONOLOGUE_ENTERPRISE_API_KEY" \
  --form "sentiment=dislike"

When the user has consented to share the example for quality review and model improvement, attach the final text, audio, or both:

curl --request POST \
  --url https://go.monologue.to/v1/enterprise/transcriptions/TRANSCRIPTION_ID/feedback \
  --header "X-API-Key: $MONOLOGUE_ENTERPRISE_API_KEY" \
  --form "sentiment=dislike" \
  --form "text=The final text shown to the user" \
  --form "audio=@dictation.m4a"

The API returns 201 Created after storing the feedback:

{
  "feedback_id": "0f85a9bf-3a70-4f21-a752-bf85020f3945",
  "transcription_id": "TRANSCRIPTION_ID",
  "sentiment": "dislike"
}

Keep the client contract small

Do not resend timestamps, platform, app version, duration, raw text, context, dictionary, instructions, or custom metadata. Monologue joins the feedback to existing usage metadata through the transcription ID.

Dictation is still metadata-only by default. A feedback submission always stores its thumb and identifiers. Optional text or audio is stored only when your client explicitly attaches it.

Client tokens work for browser, mobile, and desktop feedback requests. Never embed a long-lived enterprise API key in a client application.