The WebApp and the API provide information about the status of your sources. The objective is to ensure you have visibility on the content (input feeds) used in your broadpeak.io Services definitions.
The API call you need to use to Check the status of a source is the following one:
200: The status details
400: The source has an unknown manifest format
The source status displayed by the WebApp is based upon server side and client side checks.
The first check is performed server side. The client side check is done only if the server side test passes.
As client side check are impacted by web browser policies (e.g. security), a warning on the WebApp does not necessarily mean that your source is going to have the same status when used by the broadpeak.io platform.
Wherever a colored icon is displayed next to a source in the WebApp, it is reflecting the source status. In this case, by default, the refresh period is 4 seconds. If you hover your mouse over this icon, you will get additional information thanks to a tool tip. Note that source status will soon be added in the list of sources (link)
List of typical source statuses
|Status||Color code||Sample source URL||Description|
|Status OK||Green||https://origin.broadpeak.io/bpk-tv/bo2/default/index.mpd||Manifest can be read|
|Client side connectivity issue||Yellow||http://origin.broapeak.io/bpk-tv/bo2/default/index.mpd||Manifest can be read on server side but not on client side|
|Request failed with status code 404||Red||https://origin.broadpeak.io/bpk-tv/bo/default/index.m3u8||Manifest not found on the origin or CDN|
|Status failed with status code 403||Red||https://api.broadpeak.io/v1/sources/check/index.m3u8||The provided source URL requires authentication or authorization|
|Timeout of 2900 ms exceeded||Red||https://tmp.ridgeline.fr/badmanifest.m3u8||Manifest reading takes too long|
For live sources, there are 3 possible statuses:
In the Preview, the source status is highlighted as shown below
Updated 5 months ago