For calls to: /CMD_JSON_LANG?domain=domain.com&&json=yes&request=global&show%5Fextra=yes where it must have: request=global show_extra=yes Additional JSON output will be included: "recent_tickets": { "000005329": { "from": "diradmin", "id": "000005329", "name": "Message System", "new": "yes", "priority": "30", "status": "open", "subject": "Warning: The disk usage for one or more of your partitions is running low", "timestamp": "1617300055", "type": "message", "user": "multiple" }, "000005330": { "from": "diradmin", "id": "000005330", "name": "Message System", "new": "yes", "priority": "30", "status": "open", "subject": "Warning: The disk usage for one or more of your partitions is running low", "timestamp": "1617300061", "type": "message", "user": "multiple" }, "000005331": { "from": "diradmin", "id": "000005331", "name": "Message System", "new": "yes", "priority": "30", "status": "open", "subject": "User quotauser has used up 0.0% of their bandwidth and 680% of their allocated disk space", "timestamp": "1617300139", "type": "message", "user": "multiple" } } The "recent_tickets" array hold 3 arrays, one for each of the last 3 messages/tickets. Where the contents of each ticket ID will be: id=12345 #The tail -n1 of the User's ticket.list file. new=yes|no #seen or not, taken from tickets.list value. Everything else, a dump of data/tickets/123/12345/000.conf Note, it will only ever show the last entry from the tickets.list. If an old ticket has a new reply, where there are other new messages/tickets, that reply won't be reflected. It only shows the details of the higher-numbered value from the tickets.list (the last entry) ----- EVO2065