The GET /transactions endpoint allows retrieval of:

  • transaction hashes that you received through the 'Callback' requests
  • transaction promises that you received on ticket engine responses

Maximum of 100 transaction hash/promise objects can be handled on each request.

Possible error codes:

  • "error": "invalid_transaction_hash"
  • "error": "transaction_not_found"
  • "error": "invalid_transaction_promise"
  • "error": "transaction_promise_not_found"
  • "error": "unknown"

Returned Data

Events

  • accountPublicKeyHash - unique blockchain account on which the event lives. All ticket actions for this event will reference it.

Tickets

All ticket related responses will contain the following keys:

  • nftIndex - unique and immutable integer that identifies the ticket on the blockchain. Can be used to search for the ticket in the GET Protocol Ticket Explorer.

Sold Tickets

  • to - unique account blockchain address where the ticket was sent to. Can be used to search for the ticket in the GET Protocol Ticket Explorer.

Resold Tickets

  • from - unique account blockchain address where the ticket was moved from. Can be used to search for the ticket moved in the GET Protocol Ticket Explorer.
  • to - unique account blockchain address where the ticket was sent to. Can be used to search for the ticket in the GET Protocol Ticket Explorer.

Scanned Tickets

  • from - unique account blockchain address where the ticket was scanned from. No move will occur so the ticket will still sit in the same address after scan. Can be used to search for the ticket in the GET Protocol Ticket Explorer.

Invalidated Tickets

  • from - unique account blockchain address where the ticket was invalidated from. No move will occur so the ticket will still sit in the same address after invalidate. Can be used to search for the ticket in the GET Protocol Ticket Explorer.
Language
Authentication
Header
Response
Click Try It! to start a request and see the response here!