Dailymotion API
enable_click_to_unmute body parameter removal
Stopped workingSubscribe to Dailymotion APIShare
On September 28, 2026, the Dailymotion API removed the body parameter enable_click_to_unmute. Calls sending this parameter fail since that day, returning a 400 Bad Request error. The setting no longer affects player behavior.
Calls it hits
body parameter enable_click_to_unmute
What to use instead of these calls
Remove the setting from your requests. To start the player without sound, set playback.enable_mute through API v2 using PATCH /v2/players/{player_id}.
In Dailymotion API's words
They no longer affect Player behavior and will return 400 Bad Request after sunset date (Sept. 28th 2026).
Facts
- API
- Dailymotion API
api.dailymotion.com - Kind
- Parameter removal
- Announced
- September 21, 2026
- Takes effect
- September 28, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Dailymotion API's own pages
Questions
When does this change take effect?
Calls to body parameter enable_click_to_unmute on Dailymotion API stopped working on September 28, 2026.
What happens to calls after September 28, 2026?
They have failed since September 28, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Dailymotion API 1
-
body parameter enable_tap_to_unmuteParameter removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.