REST API Overview - Revision history

Glenn: /* Authentication */

2022-07-05T07:55:42Z

‎Authentication

Glenn: /* Authentication */

2022-07-05T07:55:27Z

‎Authentication

Vmurrell: /* Examples */

2021-03-27T10:38:27Z

‎Examples

Vmurrell: /* Parameters used for identifying a resource */

2021-03-27T10:36:48Z

‎Parameters used for identifying a resource

Vmurrell at 10:35, 27 March 2021

2021-03-27T10:35:11Z

Glenn: /* Implementation of the SDMX REST API in Fusion Metadata Registry */

2021-03-19T15:27:29Z

‎Implementation of the SDMX REST API in Fusion Metadata Registry

Glenn: /* Implementation of the SDMX REST API in Fusion Metadata Registry */

2021-03-19T15:27:11Z

‎Implementation of the SDMX REST API in Fusion Metadata Registry

Glenn: /* Implementation of the SDMX REST API in Fusion Metadata Registry */

2021-03-19T15:26:56Z

‎Implementation of the SDMX REST API in Fusion Metadata Registry

Glenn: /* Implementation of the SDMX REST API in Fusion Metadata Registry */

2021-03-19T15:26:45Z

‎Implementation of the SDMX REST API in Fusion Metadata Registry

Glenn: /* Structural Metadata Queries */

2021-03-19T15:24:16Z

‎Structural Metadata Queries

@@ Line 469: / Line 469: @@
 ====Authentication====
-Only authenticated users with sufficient Agency or Admin privileges can modify structural metadata content. HTTP Basic Authentication or Certificate Authentication must be used to with this service.
+Only authenticated users with sufficient Agency or Admin privileges can modify structural metadata content. HTTP Basic Authentication must be used to with this service.
 ====Response====
 A successful submission results in a SDMX-ML SubmitStructureResponse message.
 If an error occurs, a SDMX-ML ErrorResponseDocument is returned.

@@ Line 411: / Line 411: @@
 ====Authentication====
-Only authenticated users with sufficient Agency or Admin privileges can modify structural metadata content. HTTP Basic Authentication or Certificate Authentication must be used to with this service.
+Only authenticated users with sufficient Agency or Admin privileges can modify structural metadata content. HTTP Basic Authentication must be used to with this service.
 ====Actions====

@@ Line 313: / Line 313: @@
 <li><p>To retrieve the category PRICES of the DOMAINS category scheme maintained by the ECB, as well as the categorisations referencing that category:</p>
 <pre>http://ws-entry-point/categoryscheme/ECB/DOMAINS/latest/PRICES?references=categorisation</pre></li>
-<li><p>To retrieve the latest version of the CL_FREQ codelists maintained by the BIS or the ECB: http://ws-entry-point/codelist/BIS+ECB/CL_FREQ</p></li></ul>
+<li><p>To retrieve the latest version of the CL_FREQ codelists maintained by the BIS or the ECB: <nowiki>http://ws-entry-point/codelist/BIS+ECB/CL_FREQ</p></li></ul></nowiki>
 = Schema queries =

@@ Line 143: / Line 143: @@
 * If no version is specified, the version currently used in production should be returned. It is therefore equivalent to using the keyword <code>latest</code>.
-* If no agencyID is specified, the matching artefacts maintained by any maintenance agency should be returned. It is therefore equivalent to using the keyword <code>all</code>. This would potentially return more than one artefact, if different agencies give the same identifier to a resource (for example, http://ws-entry-point/codelist/all/CL_FREQ, could return more than one codelist if more than one agency is maintaining a codelist with id &quot;CL_FREQ&quot;).
+* If no agencyID is specified, the matching artefacts maintained by any maintenance agency should be returned. It is therefore equivalent to using the keyword <code>all</code>. This would potentially return more than one artefact, if different agencies give the same identifier to a resource (for example, <nowiki>http://ws-entry-point/codelist/all/CL_FREQ</nowiki>, could return more than one codelist if more than one agency is maintaining a codelist with id &quot;CL_FREQ&quot;).
 * If no resourceID is specified, all matching artefacts (according to the other criteria used) should be returned. It's is therefore equivalent to using the keyword <code>all</code>.
 * If no parameters are specified, the '''latest''' version of '''all''' resources of the type identified by the resource parameter, maintained by '''any''' maintenance agency should be returned.

← Older revision		Revision as of 10:35, 27 March 2021
Line 1:		Line 1:
	[[Category:FMR_REST_API_Reference]]		[[Category:FMR_REST_API_Reference]]
−
	=SDMX Standard REST API Specification=		=SDMX Standard REST API Specification=

@@ Line 25: / Line 25: @@
 | Structural Metadata Queries || style="backgroundcolor:red;" | YES
 |-
-| Schema Queries (for SDMX-ML Structure Specific Data validation schemas) || YES
+| Schema Queries (for retrieving SDMX-ML Structure Specific Data validation schemas) || YES
 |-
 | Data Queries || NO

@@ Line 55: / Line 55: @@
 = Structural Metadata Queries =
-GET with the following general URL syntax:
+A structural metadata query uses HTTP GET with the following general URL syntax:
-<pre>protocol://ws-entry-point/resource/agencyID/resourceID/version</pre>
+<pre>http(s)://ws-entry-point/resource/agencyID/resourceID/version</pre>
 === Resources ===