Show an email

GET /hyperkitty/api/list/[email protected]/email/7QAOEIZV6IU2WKT7OKPYAIQUKPYMIWEW/
HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/7QAOEIZV6IU2WKT7OKPYAIQUKPYMIWEW/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "7QAOEIZV6IU2WKT7OKPYAIQUKPYMIWEW",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/7QAOEIZV6IU2WKT7OKPYAIQUKPYMIWEW/",
    "sender": {
        "address": "pyantis (a) earthlink.net",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Perry Yantis",
    "subject": "[amsat-bb]  Still having problems with the new kep format??",
    "date": "2006-10-27T18:05:46Z",
    "parent": null,
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/CUQKFNCCLYTYSI2XDSTI5UW6YGQWSI32/"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "\nCan anyone tell my why Celestian bbs changed it kep format from something\nsimple and easy to use to something that don't work!!!!\n\nAgain today I have downloaded the new keps, then in Word Pad deleted the\nsatellites I don't want and the +-[] that I don't want and resaved the file.\n\nBut once again my sat programs reject these new files.\n\nI may start using the Amsat keps that are in the NASAbare files as these\nare text without extra stuff.\n\nThe problem with these keps are the sat names are different from what I\nhave in my programs now (nova and Uni-trak) and as a result\nI will have to re enter all the satellites.\n\nAs a result I am very ticked off that things were changed that cause all\nthese problems.\n\nWhy can't the sat keps be simple text files that all use the same names and\nno extra stuff.\n\nThis should not be this much of a problem.\n\nPerry WB8OTH\n\n\nPerry Yantis\[email protected]\n\n\n",
    "attachments": []
}