Difference between revisions of "Transaction Web Service"
Jump to navigation
Jump to search
(Created page with "= Overview = The Transaction Web Service provides access to all the structural metadata content of the Fusion Registry (including any content that has been subsequently delet...") |
(→Overview) |
||
| Line 7: | Line 7: | ||
|style="background-color:#eaecf0"|<b>Entry Point</b>|| <b> /ws/registry/tx/searchTransactions</b> | |style="background-color:#eaecf0"|<b>Entry Point</b>|| <b> /ws/registry/tx/searchTransactions</b> | ||
|- | |- | ||
| − | |style="background-color:#eaecf0"|<b>Access</b>|| <span style='color: | + | |style="background-color:#eaecf0"|<b>Access</b>|| <span style='color:green'><b>Public</b></span> |
|- | |- | ||
|style="background-color:#eaecf0"|<b>Http Method</b>|| GET | |style="background-color:#eaecf0"|<b>Http Method</b>|| GET | ||
Revision as of 01:50, 4 February 2021
Overview
The Transaction Web Service provides access to all the structural metadata content of the Fusion Registry (including any content that has been subsequently deleted). A Transaction is the submission of a structure, group of structures or data registration.
| Entry Point | /ws/registry/tx/searchTransactions |
| Access | Public |
| Http Method | GET |
| Accepts | CSV, XLSX, SDMX-ML, SDMX-EDI (any format for which there is a Data Reader) |
| Compression | Zip files supported, if loading from URL gzip responses supported |
| Content-Type | 1. multipart/form-data (if attaching file) – the attached file must be in field name of uploadFile 2. application/text or application/xml (if submitting data in the body of the POST) |
| Response Format | Determined by Accept Header - default SDMX 2.1 Structure Specific |
| Response Statuses | 200 - Submisson Accepted 400 - Submission could not be performed (either an unreadable dataset, or unresolvable reference to a required structure) 401 - Unauthorized (if access has been restricted) 500 - Server Error |
