Announced deprecations
As we are constantly improving Dailymotion’s products in order to provide you with quality services in line with the most advanced technologies on the market, some features may become obsolete over time and need to be replaced by new solutions.
In this article, we are keeping an up-to-date list of announced feature deprecations (from August 2024) with deprecation and sunset dates, detailed descriptions and recommended actions to help you migrate to newer solutions.
The status of the announced deprecations are defined as follows:
- ⚠️ Deprecation: We no longer support this feature. An upcoming sunset date will be communicated. If you are currently using a feature in deprecation, please follow the recommended actions provided.
- ⛔ Sunset: This feature will cease to work from the specified sunset date.
SDK deprecations
SDK | Deprecation date | Sunset date | Notes |
---|---|---|---|
AMP SDK | January 2024 | October 15th 2024 | We recommend migrating to our other integration methods for web |
Legacy iOS SDK | March 2023 | February 3rd 2025 | Use the new iOS SDK → Migration guide |
Legacy Android SDK | July 2023 | February 3rd 2025 | Use the new Android SDK → Migration guide |
Feature deprecations
The table below provides an overview of the feature deprecations with their respective deprecation and sunset dates.
Details about each feature deprecations along with descriptions and recommended actions to help with the transition can be found below the table.
Feature | Deprecation date | Sunset date | Notes |
---|---|---|---|
⚠️ Deprecation of legacy embed endpoint | September 23rd 2024 | February 3rd 2025 | Legacy embed endpoint www.dailymotion.com/embed/video/VIDEO_ID is being progressively deprecated.See more details. |
⚠️ Deprecation of legacy embed endpoint
Summary
The legacy embed endpoint is being progressively deprecated and replaced with our new embed endpoint:
Legacy embed endpoint | www.dailymotion.com/embed/video/VIDEO_ID |
New embed endpoint | https://geo.dailymotion.com/player/PLAYER_ID.html?video=VIDEO_ID |
Since this deprecation can have a significant impact on integrations, we are proceeding with a progressive deprecation to allow Partners to complete the migration without disruption.
Why are we deprecating the legacy embed endpoint?
So that you can upgrade your integration and enjoy the benefits that comes with the new embed endpoint:
- Use your custom Player configuration and manage settings from your Studio
- Improved viewability measurement
- Optimized monetization with custom parameters and more accurate ad targeting
Timeline
Deprecation date | September 23rd 2024: Start of the progressive deprecation plan. See below detailed timeline of the progressive deprecation plan. |
Sunset date | From February 3rd 2025: Legacy embed endpoint will be cleaned up from our codebase and will redirect to new embed endpoint with default Player settings |
Progressive deprecation plan
As the deprecation of the legacy embed endpoint is impacting several elements within our API and the legacy embed flow, we are proceeding with a progressive deprecation.
To help you take the necessary actions, the table below details the deprecation timeline for each impacted element. Please refer to the sections that are relevant to your integration and take the necessary steps to migrate accordingly.
Impacted elements | Summary | Timeline |
---|---|---|
API field embed_html | REST API response for embed_html will return new embed endpoint → Migration guide | From September 23rd 2024 |
API field embed_url | REST API response for embed_url will return new embed endpoint → Migration guide | From September 23rd 2024 |
Video and playlist embedded on web | Videos or playlists embedded with the legacy embed endpoint on web will automatically be redirected to the new embed endpoint. → Migration guide | From October 15th 2024 |
Video and playlists embedded on native | Videos or playlists embedded with our legacy native SDKs (Android, iOS) will be sunset and will no longer load the Player, as they rely on the deprecated embed endpoint. Migration to our currently supported native SDKs is required: → Android migration guide → iOS migration guide | From February 3rd 2025 |