Reference Metadata API

See Reference Metadata

Overview

This API supports GET (retrieve reference metadata), POST (submit new or modified reports), and DELETE (remove existing reports) methods to maintain Reference Metadata Reports.

The GET methods conform to the SDMX REST Specification for reference metadata retrieval.

GET Reference Metadata

Entry Point	/sdmx/v2/metadata
Access	Public
Http Method	GET
Response Format	JSON
Response Statuses	200 - Success 401 - Unauthorized (if access has been restricted) 500 - Server Error

See Specification.

Examples

Get specific report

https://example.registry.com/sdmx/v2/metadata/metadataset/MT/REPORT1/1.0

Get all metadata sets for a specific Metadata Provider

https://example.registry.com/sdmx/v2/metadata/metadataset/MT.PROVIDER/*/*

Get all reports against Metadataflow as Stubs (only include basic details, not the actual reported content)

https://example.registry.com/sdmx/v2/metadata/metadataflow/MT/MDF1/1.0?detail=allStubs

Get all reports against Metadataflow for a specific Metadata Provider

https://example.registry.com/sdmx/v2/metadata/metadataflow/MT/MDF1/1.0/PROVIDER1

Get all reports against any BIS Codelist

https://example.registry.com/sdmx/v2/metadata/strucure/codelist/BIS

POST Reference Metadata

Entry Point (11.6.0 onwards)	/ws/secure/sdmx/v2/metadata
Entry Point (pre 11.6.0)	/sdmx/v2/metadata
Access	Public
Http Method	POST
Accepts	SDMX-JSON
Content-Type	1. multipart/form-data (if attaching file) – the attached file must be in field name of uploadFile 2. application/text or application/json (if submitting data in the body of the POST)
Response Format	N/A
Response Statuses	200 - Success 401 - Unauthorized (if access has been restricted) 500 - Server Error

Submit a Reference Metadata report, on success an HTTP 200 status is returned. On failure an SDMX Error message is returned with the HTTP status code set to the appropriate code.

Example Error:

<?xml version="1.0" ?>
<message:Error xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:message="http://www.sdmx.org/resources/sdmxml/schemas/v2_1/message" xmlns:com="http://www.sdmx.org/resources/sdmxml/schemas/v2_1/common">
 <message:ErrorMessage code="100">
   <com:Text>Could not resolve reference from structure Metadata Set 'MT:EXAMPLE1.0.0)' to structure Metadata Provision Agreement 'MT:MUK1_EXAMPLE(1.0)'</com:Text>
 </message:ErrorMessage>
</message:Error>

DELETE Reference Metadata

Entry Point	/sdmx/v2/metadata
Access	Public
Http Method	DELETE
Response Format
Response Statuses	200 - Success 401 - Unauthorized (if access has been restricted) 500 - Server Error

Deletes all reference metadata reports which match the query URL, the path parameters following the /metadata/ are used to create a filter on the Metadata Reports. The path uses the same syntax as the GET parameters, it is therefore possible to delete by specific report identifiers, by metadataflow, or by structure query.

Examples

Delete specific report

https://example.registry.com/sdmx/v2/metadata/metadataset/MT/REPORT1/1.0

Delete all versions of report

https://example.registry.com/sdmx/v2/metadata/metadataset/MT/REPORT1/*

Delete all reports against Metadataflow

https://example.registry.com/sdmx/v2/metadata/metadataflow/MT/MDF1/1.0

Delete all reports against Metadataflow for a specific Metadata Provider

https://example.registry.com/sdmx/v2/metadata/metadataflow/MT/MDF1/1.0/PROVIDER1

Delete all reports against all BIS Codelists

https://example.registry.com/sdmx/v2/metadata/strucure/codelist/BIS