Difference between revisions of "Transaction Web Service"
Jump to navigation
Jump to search
(→HTTP Query Parameters) |
|||
| Line 22: | Line 22: | ||
!| Request Parameter || Required || Purpose | !| Request Parameter || Required || Purpose | ||
|- | |- | ||
| − | |style="background-color:#eaecf0"|<b> | + | |style="background-color:#eaecf0"|<b>action</b> || No || ... |
|- | |- | ||
| − | |style="background-color:#eaecf0"|<b>dateFrom</b> || No || Filters the | + | |style="background-color:#eaecf0"|<b>dateFrom</b> || No || Filters the response to only include Transactions from the specified time. The value must be specified as the epoch time in milliseconds (e.g. 1609459200000 is the start of the year 2021). |
|- | |- | ||
| − | |style="background-color:#eaecf0"|<b>dateTo</b> || No || ... | + | |style="background-color:#eaecf0"|<b>dateTo</b> || No || Filters the response to only include Transactions up to the specified time. The value must be specified as the epoch time in milliseconds (e.g. 1609459200000 is the start of the year 2021). |
|- | |- | ||
| − | |style="background-color:#eaecf0"|<b> | + | |style="background-color:#eaecf0"|<b>max</b> || No || Limits the returned response to only containing at most the specified value. |
| − | |||
| − | |||
|- | |- | ||
| − | |style="background-color:#eaecf0"|<b>orderDesc</b> || No || . | + | |style="background-color:#eaecf0"|<b>orderDesc</b> || No || The default output is that Transactions are returned in a descending order (most recent first). Supplying ''false'' to this parameter reverses the order. |
|- | |- | ||
| − | |style="background-color:#eaecf0"|<b> | + | |style="background-color:#eaecf0"|<b>user</b> || No || Filters the response to only include Transactions for the specified user. If the user could not be found empty JSON is returned. |
|} | |} | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 02:16, 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 |
| Response Format | application/json |
| Response Statuses | 200 - Submission Accepted |
HTTP Query Parameters
If no parameters are supplied all transactions known to the Registry will be returned.
| Request Parameter | Required | Purpose |
|---|---|---|
| action | No | ... |
| dateFrom | No | Filters the response to only include Transactions from the specified time. The value must be specified as the epoch time in milliseconds (e.g. 1609459200000 is the start of the year 2021). |
| dateTo | No | Filters the response to only include Transactions up to the specified time. The value must be specified as the epoch time in milliseconds (e.g. 1609459200000 is the start of the year 2021). |
| max | No | Limits the returned response to only containing at most the specified value. |
| orderDesc | No | The default output is that Transactions are returned in a descending order (most recent first). Supplying false to this parameter reverses the order. |
| user | No | Filters the response to only include Transactions for the specified user. If the user could not be found empty JSON is returned. |
