...
Depending on the request, a data query can result in a (potentially very) large response in which case data is delivered asynchronously. For more information please read the page 'API getting started' for the section about ASYNC endpoint
This is the SDMX 2.1 REST request for data:
...
Parameter | Description |
api_base_uri | |
resource | Following resource is supported: data |
flowRef | The identifier of the dataflow reference. |
Optional | Description |
key | The key in the query is constructed as a dot ('.') separated list of dimension filtered values. |
parameters | Multiple parameters can be combined by means of '&' character. |
Format | |
Data filtering on time | |
Data filtering on first N and last N observations | |
Details | |
Compression |
...
Retrieving data in SDMX-ML Generic Data format using REST from the SDMX 2.1 endpoint.
Example |
...
Retrieving data in SDMX-ML Structure Specific Data format using REST from the SDMX 2.1 endpoint.
Example |
...
| Tip |
|---|
In SDMX-CSV, the response contains the data displayed in a flat format. It includes codes, and not labels, for dimensions positions. The labels equivalent to codes can be resolved by requesting the dataflow or data structure definition with references resolution. |
Retrieving data in SDMX-CSV format using REST from the SDMX 2.1 endpoint.
...
Retrieving data in JSON-stat format in English using REST from the SDMX 2.1 endpoint.
Example |
...
| Tip |
|---|
In TSV, the response includes codes, and not labels, for dimensions positions. The labels equivalent to codes can be resolved by requesting the dataflow or data structure definition with references resolution. |
Retrieving data in TSV format using REST from the SDMX 2.1 endpoint.