Browse availability
Narrow down which codes are actually usable for one dimension, once other dimensions of the key are already fixed — useful for building valid keys interactively instead of guessing.
//JAVA 25+
//DEPS com.github.nbbrd.sdmx-dl:sdmx-dl-standalone:3.2.0
import sdmxdl.*;
import sdmxdl.web.SdmxWebManager;
void main() throws Exception {
SdmxWebManager
.ofServiceLoader()
.usingName("ECB")
.listAvailability(AvailabilityRequest.builder()
.flowOf("EXR")
.keyOf("M..EUR.SP00.A")
.dimension("FREQ")
.build())
.forEach((code, label) -> IO.println(code + " = " + label));
}
sdmx-dl list availability ECB EXR M..EUR.SP00.A 1
- Unlike Browse codes, this only returns codes that actually occur in the data under the given constraint — not every code defined in the codelist.
- The dimension is not referenced the same way across flavors: the API and WS (
AvailabilityRequest.dimension/gRPCdimensionfield/REST/availability/{dimension}path segment) take the dimension by its id (e.g.FREQ, as returned by Browse dimensions and attributes), while the CLI conveniently accepts a zero-based index into the key instead (e.g.1for the second component ofM..EUR.SP00.A) and resolves it to an id internally before calling the same request.