"\n\n\n\n \n\tDocumentation\n\t\n\n\n
\n\n \n\n

Transaction webservice

\n
\n\n \t\t

   The transaction webservice allows to retrieve information about the data integration transactions of Nodes A. There are three detail levels:\n \t\t

    \n \t\t
  1. Transaction level : With this level general transactions informations are requested.
    2. \n \t\t
  2. File level : With file level, we will have informations about the files of the transaction \"transcationsid\".The transactionid argument is mandatory.
    3. \n \t\t
  3. Content level : Displays the XML file of the transaction. The transactionid argument is mandatory.
    4. \n \t\t
\n
A query without parameters returns the hundred last transactions.\n

\n

Overview of request parameters

\n

The request parameters for service are summarized in table below.

\n
\n \t\t \t\n \t\t \t\t\n \t\t \t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\n \t\t \t\t\n \t\t \t\t\n \t\t \t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\n \t\t \t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\n\t\t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\n\t\t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\n\t\t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\n\t\t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\n\t\t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\n\t\t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\n\t\t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\n\t\t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\t\n \t\t \t\t\t\n \t\t \t\t\n \t\t \t
ParameterRequiredDescriptionValues (default)
starttimeNOTransaction limit date at or after the specific start timeYYYY-MM-DDTHH:MM:SS (-)
endtimeNOLimit transaction date at or before the specific end timeYYYY-MM-DDTHH:MM:SS (-)
nodeNONode name in capital lettersOMIV, IPGP, RAP, SISMOB, DASE, RLBP-OCA, RLBP
networkNOFDSN network code Network codes list is available here
statusNOTransaction status(*)
typeNOTransaction typeseismic_data_miniseed\n / seismic_metadata_dataless_seed (*)
formatNOOutput formattext/json (json)
transactionidNOTransaction ID (-)
erroronNOID of the test causing the error (-)
levelNODetail leveltransaction/file/content (transaction)
\n\n

HTTP status codes

\n\n

Table below includes a list of codes status returned by the webservice. These codes should be used by end-users to check if a request was successful.

\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
CodeDescription
200Successfull request, result follow
201Request was properly formatted and submitted but no data match the selection
400Bad request due to improper specification, unrecognized parameter, etc.
203Request resulted in too much data being returned or the request itself is too large.
500Internal Server Error.
\n\n
\n
\n

Examples

\n\n
\n\n \n\n
\n
\n
\n\n\n"