Genesys Cloud - Developer Announcements!

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Deprecation of mediaTranscriptions Field in Media Retention Policy APIs

  • 1.  Deprecation of mediaTranscriptions Field in Media Retention Policy APIs

    Posted 16 hours ago

    Summary

    The mediaTranscriptions field within the Media Retention Policy APIs is being deprecated and will be removed on or after August 3, 2026.

    This field was previously used to configure the Voci and Call Journey third-party transcription integrations. As these integrations are no longer supported, the field is no longer functional.

    During the deprecation period:

    • The mediaTranscriptions field will continue to appear in API responses but will always be null.
    • Any value supplied for mediaTranscriptions in POST, PUT, or PATCH requests will be silently ignored.

    Effective Date

    Friday, June 5, 2026

    Details

    The Voci and Call Journey AppFoundry transcription integrations have been deprecated and removed from the platform.

    As a result, the mediaTranscriptions field on:

    • policy.mediaPolicies.callPolicy.actions
    • policy.mediaPolicies.chatPolicy.actions
    • policy.mediaPolicies.emailPolicy.actions
    • policy.mediaPolicies.messagePolicy.actions

    is no longer used by the platform.

    The platform has already stopped:

    • Populating the field in API responses.
    • Persisting values supplied in API requests.

    After the removal date:

    • The mediaTranscriptions field will be removed from the API response schema.
    • Requests containing mediaTranscriptions will fail schema validation.
    • Generated SDKs referencing mediaTranscriptions, MediaTranscription, or TranscriptionProvider (VOCI, CALLJOURNEY) will need to be regenerated, and any references removed from customer integrations.

    Customer Impact

    • Reads (GET) — the mediaTranscriptions field is already null in responses today and will stay that way until removal. Consumers that null-check the field need no action.
    • Writes (POST / PUT / PATCH) — any mediaTranscriptions value sent in the request body is silently ignored by the platform. On the next policy update, the field is stripped from storage. No 400 is returned during the notice window.
    • After removal — requests that include mediaTranscriptions will return a schema validation error. Customers who still send the field in their automation should remove it from their request bodies before the removal date. Customers who read the field can remove the parsing code at their convenience.
    • No replacement field is required. Customers needing transcription should use Genesys Cloud's native transcription capability.

    Replacement Guidance

    No replacement field is required. Customers requiring transcription capabilities should use Genesys Cloud native transcription functionality.

    Impacted Resources

    • GET /api/v2/recording/mediaretentionpolicies
    • POST /api/v2/recording/mediaretentionpolicies
    • GET /api/v2/recording/mediaretentionpolicies/{policyId}
    • PUT /api/v2/recording/mediaretentionpolicies/{policyId}
    • PATCH /api/v2/recording/mediaretentionpolicies/{policyId}

    Issue References

    WEM-1451

    Contacts

    @Karthiga Chellamuthu  

    Please reply to this announcement with any questions. This helps the wider developer community benefit from the discussion. We encourage you to use this thread before contacting the designated person directly. Thank you for your understanding.



Related Content