POST /v0/updates
Deprecated, use /v2/updates instead. Returns the update history in ascending order, paged, from ledger begin or optionally starting after a record time.
Body
The maximum number of transactions returned for this request.
The transactions returned will either have a higher migration id or the same migration id and a record_time greater than the migration id and record time specified.
Whether contract payload should be encoded into json using a lossless, but much harder to process, encoding. This is mostly used for backend calls, and is not recommended for external users. Optional and defaults to false.
Response
ok
An individual item in the update history. May be a transaction or a contract reassignment.
- Option 1
- Option 2