Show an email

GET /hyperkitty/api/list/[email protected]/email/WG6UPM25P47SLYQYK7VNRHOJW4LQEKKK/?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/WG6UPM25P47SLYQYK7VNRHOJW4LQEKKK/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "WG6UPM25P47SLYQYK7VNRHOJW4LQEKKK",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/FYUIN63VR6VLBXLPAYSEVPYAFQXONECZ/?format=api",
    "sender": {
        "address": "kq6ea (a) verizon.net",
        "mailman_id": "d2ef86d749ee450c8ad9ffc9f2e15cad",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/d2ef86d749ee450c8ad9ffc9f2e15cad/emails/?format=api"
    },
    "sender_name": "Jim Jerzycke",
    "subject": "Re: [amsat-bb] W7O update",
    "date": "2014-11-18T06:01:08Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/SZNZWHV32QDG6TF4LLTJTFUAUBBIC36R/?format=api",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/UIHCD3TPCHXH4QVQ2HGN7US4JWRW2WUD/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Our FCC will issue a \"Special Event\" callsign for these uses.\n\n100% legal.\n\n73, Jim  KQ6EA\n\nOn 11/18/2014 05:40 AM, Gus wrote:\n> On 11/17/2014 11:38 PM, Patrick STODDARD (WD9EWK/VA7EWK) wrote:\n>> So far, so good. Lots of operators have been helping\n>> out by operating as W7O, on the satellites and the HF\n>> bands.\n>\n> How does that happen?  Is there not a statutory requirement that \n> theoperators in question use their own callsigns? I understand using a \n> club call at a club station, but surely operators all over the place \n> can't simply decide to use whatever call they feel like, all at once, \n> whenever they like?\n>\n\n",
    "attachments": []
}