Response schema changed for POST /v2/transcript (TranscriptParams)

What changed

Response schema changed for POST /v2/transcript (TranscriptParams) Affected surface: POST /v2/transcript. Root cause: schema `TranscriptParams`. Detected at Tue, 02 Jun 2026 02:41:13 UTC UTC.

Diff

{
  "path": "POST /v2/transcript",
  "removed_fields": [
    "language_detection",
    "summary_type",
    "speech_understanding",
    "entity_detection",
    "redact_pii_sub",
    "content_safety_confidence",
    "filter_profanity",
    "webhook_url",
    "summarization",
    "multichannel",
    "custom_spelling",
    "redact_pii",
    "language_confidence_threshold",
    "language_codes",
    "redact_pii_policies",
    "webhook_auth_header_value",
    "redact_pii_audio",
    "remove_audio_tags",
    "audio_url",
    "keyterms_prompt",
    "language_detection_options",
    "redact_pii_audio_quality",
    "temperature",
    "prompt",
    "auto_highlights",
    "speaker_labels",
    "auto_chapters",
    "redact_pii_return_unredacted",
    "sentiment_analysis",
    "summary_model",
    "language_code",
    "webhook_auth_header_name",
    "punctuate",
    "speaker_options",
    "speakers_expected",
    "content_safety",
    "speech_models",
    "speech_threshold",
    "audio_end_at",
    "custom_topics",
    "format_text",
    "topics",
    "speech_model",
    "redact_pii_audio_options",
    "iab_categories",
    "disfluencies",
    "audio_start_from",
    "domain"
  ],
  "schema_path": "schema TranscriptParams"
}

Likely impact

The contract still holds, but observable behavior shifted — defaults, response timing, or rate-limit shaping. Existing code keeps compiling and most calls keep working, but edge cases may differ. Worth a sanity check.

Recommended action

Diff your serializers against the new schema. The diff above shows what moved.