Difference between revisions of "Query Structures Web Service"

From FMR Knowledge Base
Jump to navigation Jump to search
(Headers)
(Headers)
Line 38: Line 38:
 
</ul>
 
</ul>
 
|-
 
|-
|style="background-color:#eaecf0"|<b>Accept</b>||  
+
|style="background-color:#eaecf0"|<b>Accept-Language</b>||  
 
This optional header can be used to set the locale to return any multilingual text in (names and
 
This optional header can be used to set the locale to return any multilingual text in (names and
 
descriptions). If the text does not
 
descriptions). If the text does not
Line 45: Line 45:
 
to find the next best appropriate
 
to find the next best appropriate
 
locale.
 
locale.
| Accept-Language : en (English)
+
|  
Accept-Language : fr (French)
+
Examples:<br>
Accept-Language : * (all languages – no filter)
+
Accept-Language : en (English)<br>
Accept-Language : all (all languages – no filter)
+
Accept-Language : fr (French<br>)
 +
Accept-Language : * (all languages – no filter)<br>
 +
Accept-Language : all (all languages – no filter)<br>
  
 
  ||
 
  ||

Revision as of 13:38, 20 January 2021

Overview

Fusion Metadata Registry provides a web service for querying structural metadata which conforms to the SDMX specification.

Some additional Accept header values and query parameters are also supported both of which are explained in this guide.

Entry Point /ws/public/sdmxapi/rest/
Access Secure Public
Authentication None
Http Method GET
Response Format Multiple SDMX formats supported which can be specified wither using the HTTP Accept header or the 'format' URL parameter
Response Statuses

200 - Success

404 - Structure not found

500 - Server Error

Error Response SDMX-ML 2.1 Error Response Document

Headers

HTTP Header Purpose Allowed Values
Accept To define the response format
  • application/vnd.sdmx.structure+edi
  • application/vnd.sdmx.structure+xml;version=1.0
  • application/vnd.sdmx.structure+xml;version=2.0
  • application/vnd.sdmx.structure+xml;version=2.1
  • application/vnd.sdmx.json
Accept-Language

This optional header can be used to set the locale to return any multilingual text in (names and descriptions). If the text does not exist in the specified locale, then the default rules will be applied to find the next best appropriate locale.

Examples:
Accept-Language : en (English)
Accept-Language : fr (French
) Accept-Language : * (all languages – no filter)
Accept-Language : all (all languages – no filter)