API, Data Model, and XSDs
A public API is available to query all published QC Test definitions (including links to the famous 'Card' images).
Example API v1 calls
https://ebu.io/qc/api/v1/items returns all published (and any deprecated) Test Items
https://ebu.io/qc/api/v1/items/0001F returns a specific Test Item
https://ebu.io/qc/api/v1/items/0001F/versions/2.0 returns a specific version of a Test Item
Fair use (rate limiting)
The API calls are limited in time & amount.
Requests also can be cached, so you may get a 429 if you already got the latest information. See the API documentation for more details.
API v1 documentation
The API documentation consists of a description and an XML Schema document:
Additional functionality
Since 01 June 2023, a flag is available that allows the export of all Items in CSV or JSON:
https://qc.ebu.io/api/v1/items?output-format=csv
https://qc.ebu.io/api/v1/items?output-format=json
If you specify an unrecognized output-format, XML will be used as the default.
If you use an unrecognized query format (e.g. misspelled 'outputformat'), you will get an emtpy result.
EBU.IO/QC Data model
The data model that forms the basis for the EBU.IO/QC system is described in the following publications:
Feedback
We welcome your feedback (questions, issues, ideas, etc.) via tech@ebu.ch
Git used for development
The data model and API specs are developed using this git (accessible to EBU QC Group participants).
API v2 (in test!)
In release QC.EBU.IO v.4.50.0 API v2 functionality has been introduced for the first time.
Note that this functionality is provided FOR TESTING only and is NOT expected to be stable, yet.
You can find the related API v2 documentation at: https://qc.ebu.io/swagger-ui/
- Exported Items by default ONLY include Item versions that are 'Published' or 'Withdrawn'.
- To override the types of Items to return, use addtional parameters (NOT documented in Swagger).
- Example: https://qc.ebu.io/api/v2/items/?status[]=drafting&status[]=published
- A similar format can be used for individual Items. Note this is DIFFERENT from what is implemented for the core API. Example:
- https://dev.ebu.io/api/v2/items/8888T/?status[]=drafting
- Contrary to before (API v1) the 'patch' (third) part of the QC Item version number is also included (this allows distinguishing between e.g. two subsequent versions of QC Items in drafting).
- Exported Parameters (Types, Representations, Units, Ranges) ONLY include the parameters flagged as 'official' in QC.EBU.IO.
- As shown in the swagger documentation, it is possible to query where specific parameter (versions) are used. Example:
https://qc.ebu.io/api/v2/representations/6/versions/1/items/