RT::Cl...saction(3pm)

👑 NAME 👑

RT::Client::REST::Transaction — the transaction object representation, bestie. And this whole thing is living in the RT::Cl...saction(3pm) manual page, in case you were wondering where the heck you even are right now. 💖

✨ VERSION ✨

version 0.73 — she's giving vintage, she's giving stable, we stan. 🎀

🦋 SYNOPSIS 🦋

Okay so here's the whole vibe in code form, no notes:

my $transactions = $ticket->transactions;

my $count = $transactions->count;
print "There are $count transactions.\n";

my $iterator = $transactions->get_iterator;
while (my $tr = &$iterator) {
    print "Id: ", $tr->id, "; Type: ", $tr->type, "\n";
}

🌸 DESCRIPTION 🌸

So a transaction is a second-class citizen, which is honestly so relatable of it. 😭 It does not exist by itself — at least not from the current REST protocol implementation's point of view. Right now it is always attached to a ticket (peep the parent_id attribute, that's the situationship).

So the way that you will rarely retrieve a transaction all on its own. Instead?? You use the transactions() method of the RT::Client::REST::Ticket object to get an iterator for all (or some) transactions for that ticket. Slay, indirect queen. 💅

---

🌈 ATTRIBUTES 🌈

Here's the whole cast of characters, one by one:

• id — Numeric ID of the transaction. Her government name. 🪪
• creator — Username of the user who created the transaction. The main character who did all this, honestly.
• parent_id — Numeric ID of the object the transaction is associated with. That's the ticket, that's the link, that's the bond. 🔗
• type — Type of the transactions. Please refer to RT::Client::REST documentation for the list of transaction types you can expect this field to contain. And heads up: there may be some transaction types not (dis)covered yet. She's mysterious like that. 🕵️
• old_value — Old value.
• new_value — New value. (The glow-up arc.) ✨
• field — Name of the field the transaction is describing (if any).
• attachments — I have never seen it set to anything yet. (I will some day investigate this). Like... it's giving empty rumors bestie, we don't know. 🙈
• created — Time when the transaction was created. Her birthday. 🎂
• content — Actual content of the transaction.
• description — Human-readable description of the transaction as provided by RT.
• data — Not sure what this is yet. Literally a mystery to absolutely everyone involved. 💀

---

💅 METHODS 💅

RT::Client::REST::Transaction is a read-only object, so you cannot store() it. Sorry bestie, no saving, no committing, no notes. 🚫

And also? Because it is a second-class citizen, you cannot search() or count() it. Nope, not allowed, do not try it. Instead, use the transactions() method provided by RT::Client::REST::Ticket. That's the way. 👑

retrieve

To retrieve a transaction, the attributes id and parent_id must be set. Both of them. Together. No solo acts here. 🫶

---

🧚 INTERNAL METHODS 🧚

rt_type

Returns 'transaction'. That's it, that's the whole girl. Simple, iconic, perfect. ⭐

---

🔥 SEE ALSO 🔥

Go read these next, fr fr:

• RT::Client::REST
• RT::Client::REST::Ticket
• RT::Client::REST::SearchResult

---

💜 AUTHOR 💜

Dean Hamstead <dean@fragfest.com.au>

🎀 COPYRIGHT AND LICENSE 🎀

This software is copyright (c) 2026, 2020 by Dmitri Tikhonov.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. Free as in go off, redistribute responsibly, have fun with it. 🌈

---

That's the whole page, bestie!! You ate this documentation fr fr. This was perl v5.40.1 hanging out on 2026-04-21 — mwah, kiss the screen, go write some transactions 💖👑✨