A transaction is a second-class citizen, as it does not exist (at least from the current REST protocol implementation) by itself. At the moment, it is always associated with a ticket (see parent_id attribute). Thus, you will rarely retrieve a transaction by itself; instead, you should use transactions() method of RT::Client::REST::Ticket object to get an iterator for all (or some) transactions for that ticket.

Type of the transactions. Please referer to RT::Client::REST documentation for the list of transaction types you can expect this field to contain. Note that there may be some transaction types not (dis)covered yet.

RT::Client::REST::Transaction is a read-only object, so you cannot store() it. Also, because it is a second-class citizen, you cannot search() or count() it -- use transactions() method provided by RT::Client::REST::Ticket.