Email Detail

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/WF5WHS4FWM7ZHUA4WW6FKFX4XYEKK5G7/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "WF5WHS4FWM7ZHUA4WW6FKFX4XYEKK5G7",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/WF5WHS4FWM7ZHUA4WW6FKFX4XYEKK5G7/",
    "sender": {
        "address": "n6elf (a) nanoloop.io",
        "mailman_id": "0aa580fa9ceb49559e2890bcdb08b802",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/0aa580fa9ceb49559e2890bcdb08b802/emails/"
    },
    "sender_name": "Ben Cook",
    "subject": "Re: [amsat-bb] AO-92 High Speed Data decode questions",
    "date": "2020-04-30T00:58:04Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "As someone new to satellite operations, I’m finding out that it’s \nextremely helpful to not only check the AMSAT status page before an \nupcoming pass, but also check reports from AMSAT and others on twitter. \nThat helps to cut down on the confusion around schedule or mode changes. \nFor example, helps to know that AO-92 was put into L mode an hour before \nthe next pass you’re planning to work. Just thoughts to myself this \nfirst week or so on the air.\n\n73,\nBen - N6ELF\n",
    "attachments": []
}