Changes to Get the opcode traces for a historical transaction on the network with the given transaction ID or hash

GET /api/v1/contracts/results/{transactionIdOrHash}/opcodes

Every recorded change to this endpoint, newest first. Back to the operation

Changed in 1 of the 53 revisions of this API.11

Aug 8, 2025v1db389f03b09711

What changed

Aug 8, 2025v1db389f03b09711See the full diff
- ▲
  the response property _status/messages/items/data became nullable for the status 400
  response-property-became-nullable
- ▲
  the response property _status/messages/items/data became nullable for the status 404
  response-property-became-nullable
- ▲
  the response property _status/messages/items/data became nullable for the status 429
  response-property-became-nullable
- ▲
  the response property _status/messages/items/detail became nullable for the status 400
  response-property-became-nullable
- ▲
  the response property _status/messages/items/detail became nullable for the status 404
  response-property-became-nullable
- ▲
  the response property _status/messages/items/detail became nullable for the status 429
  response-property-became-nullable
- ▲
  the response property contract_id became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property opcodes/items/memory became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property opcodes/items/reason became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property opcodes/items/stack became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property opcodes/items/storage became nullable for the status 200
  response-property-became-nullable
This revision also has 22 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog