Show an email

GET /hyperkitty/api/list/[email protected]/email/4HP44HG7AJ5CWXWJYYGC7NEB5OIPLBB3/?format=api
HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/4HP44HG7AJ5CWXWJYYGC7NEB5OIPLBB3/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "000001c75920$fc6288d0$c4e6fea9@WA4SCA",
    "message_id_hash": "4HP44HG7AJ5CWXWJYYGC7NEB5OIPLBB3",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/UBLTXYGTU33YQTPZJQCWXZROS36JJXKC/?format=api",
    "sender": {
        "address": "APBIDDLE (a) UNITED.NET",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Alan P. Biddle",
    "subject": "[amsat-bb] Re: AMSAT Journal",
    "date": "2007-02-25T21:07:40Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/UBLTXYGTU33YQTPZJQCWXZROS36JJXKC/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "I will really second the praise for the Journal!  I keep several years on my\nshelves for reference, as sometimes odd bits of information do not make it\nonline, or at least in a readily findable fashion.\n\nOne use I have found in helping potential new operators is to hand out a\nfolder with 2-3 years of issues, to be read for orientation.  While more\ndetailed information is available on the AMSAT sites, I have found the\narticles by people on what they are doing, and how they are doing it, often\nbrings about an \"Ah hah!\" moment.  I guess seeing real people makes it come\ntogether.\n\nSo, my question is whether the Journal is stored in a format which would\nlend itself to being made available online, as is the TAPR PSR?  Perhaps\nonly through the previous year so as not to cut into membership.  For\norientation purposes, that would be fine.\n\nAlan\nWA4SCA\n\n  \n\n\n",
    "attachments": []
}