Skip to main content
POST

Deprecated, use /v2/updates instead. Returns the update history in ascending order, paged, from ledger begin or optionally starting after a record time.

Body

application/json
object
OpenAPI type: UpdateHistoryRequestAfter.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.
number
required
OpenAPI type: integer (int32).The maximum number of transactions returned for this request.
boolean
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.

Responses

200

ok
application/json
UpdateHistoryItem[]
required

400

bad request
application/json
string
required

500

internal server error
application/json
string
required

History

Updated0.6.0

The POST /v0/updates operation changed in this snapshot.

Updated0.5.17

The POST /v0/updates operation changed in this snapshot.

Deprecated0.5.10
Added0.5.10