Breaking changes to api response #6
Description
The API has made breaking changes to the response returned when using Backblaze B2 for storage of encoded files.
Previous encodes would return a response that included a URL for the B2 location. Now that data appears to be located in the Path.
This is the new response:
[audios] => Array
(
[0] => Array
(
[tag] => audio-0-0
[profile] =>
[user_tag] =>
[storage] => Array
(
[path] => https://******** (removed for privacy)
[type] => b2
[format] => mp3
[expire] =>
[timestamp] => 2022-08-26 16:25:29
)
[url] =>
[bitrate] => 92
[meta] => Array
(
[index] => 0
[language] =>
[title] =>
[program_id] =>
[channels] => 2
[bit_rate] => 96000
[codec] => mp3
[sample_rate] => 44100
[program_ids] => Array
(
)
)
[duration] => 667.82
[size] => 7.64294
[output_format] => mp3
[error] =>
[error_description] =>
)
[1] => Array
(
[tag] => audio-1-0
[profile] =>
[user_tag] =>
[storage] => Array
(
[path] => https://******** (removed for privacy)
[type] => b2
[format] => mp3
[expire] =>
[timestamp] => 2022-08-26 16:25:29
)
[url] =>
[bitrate] => 92
[meta] => Array
(
[index] => 0
[language] =>
[title] =>
[program_id] =>
[channels] => 2
[bit_rate] => 96000
[codec] => mp3
[sample_rate] => 44100
[program_ids] => Array
(
)
)
[duration] => 667.82
[size] => 7.64294
[output_format] => mp3
[error] =>
[error_description] =>
)
)
The previous response was like this note no path info but there was a URL.
[audios] => Array
(
[0] => Array
(
[tag] => audio-0-0
[profile] =>
[user_tag] =>
[storage] => Array
(
[url_by_fileid] => https://******** (removed for privacy)
[url] => https://******** (removed for privacy)
[format] => mp3
[type] => b2
[fileid] => (removed for privacy)
[expire] =>
[timestamp] => 2022-08-26 16:31:07
)
[url] => https://******** (removed for privacy)
[bitrate] => 153
[meta] => Array
(
[index] => 0
[language] =>
[title] =>
[program_id] =>
[channels] => 2
[bit_rate] => 160000
[codec] => mp3
[sample_rate] => 44100
[program_ids] => Array
(
)
)
[duration] => 3207.05
[size] => 61.1702
[output_format] => mp3
[error] =>
[error_description] =>
)
[1] => Array
(
[tag] => audio-1-0
[profile] =>
[user_tag] =>
[storage] => Array
(
[url_by_fileid] => https://******** (removed for privacy)
[url] => https://******** (removed for privacy)
[format] => mp3
[type] => b2
[fileid] => (removed for privacy)
[expire] =>
[timestamp] => 2022-08-26 16:31:07
)
[url] => https://******** (removed for privacy)
[bitrate] => 92
[meta] => Array
(
[index] => 0
[language] =>
[title] =>
[program_id] =>
[channels] => 2
[bit_rate] => 160000
[codec] => mp3
[sample_rate] => 44100
[program_ids] => Array
(
)
)
[duration] => 3207.05
[size] => 36.7022
[output_format] => mp3
[error] =>
[error_description] =>
)
)
Some questions:
Why was this change made with NO NOTICE so people could update their apps?
Qencode has broken its own dashboard with this change. Trying to copy the URL of the encoded files from the dashboard is no longer possible. It appears you were using the URL response on your own dashboard but have not made the appropriate fix.
Companies rely on Qencode to not make breaking changes to API responses without notice. I am now scrambling and WORKING ON MY DAYS OFF because Qencode did this. Once I have this fixed I will be looking at another provider since you can clearly not be trusted.