These web services are the back-end of the MWA triggering system, described in detail Hancock et al, 2019 (https://ui.adsabs.harvard.edu/link_gateway/2019PASA...36...46H/EPRINT_PDF)
...
The rest of the observations provide the time/s to start and stop capture. All other observation details are inherited from whatever observation/s are currently in progress, or if there is no current observation, whatever the last observation used - this includes pointing direction/s and frequency settings. Note that all future observations (from the time called, through to 'end_time' or the end of the 'obstime' provided) are deleted by the triggerbuffer() call, to prevent the telescope state from being (further) changed during the capture.
- start_time: The earliest time in GPS seconds for which data should be saved - if zero, or before the earliest buffer file available save all data. This value is inclusive, so .free files later that, or starting at this time, are included.
- end_time: The latest time in GPS seconds for this data should be saved. If start_time and end_time are both zero, don't save any data. This time may be in the past. If not specified, keep capturing until 'obstime' seconds into the future, from the time of calling.
- obstime: How many seconds to keep capturing data for, after the buffer dump (from 'now' into the future, not including past data dumped from the buffers).
...