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/BT4O7UQSCSDNMEOT3AMV7ZVUW7TJ2EAA/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "BT4O7UQSCSDNMEOT3AMV7ZVUW7TJ2EAA",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/R7Q7L6GL6UZ4CIL74HPC3LSIM3JTW33B/",
    "sender": {
        "address": "kk7p (a) wavecable.com",
        "mailman_id": "ecaeda8313f54fe6b33b16a345e6ba3a",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/ecaeda8313f54fe6b33b16a345e6ba3a/emails/"
    },
    "sender_name": "Lyle Johnson",
    "subject": "[eagle] Re: Service class names",
    "date": "2006-10-08T18:55:23Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/R7Q7L6GL6UZ4CIL74HPC3LSIM3JTW33B/",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/P7HCJPFJC7HUJEUHFAMMWI6UKQ5RHG6X/"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hello Jim!\n\n>    Class A for what we used to call Class 0 (A from the old \"Analog\", \n> which we need to stamp out.)\n>    Class S for what we used to call Class 1 (S from SMS)\n>    Class V for what we used to call Class 2 (small station digital Voice)\n>    Class H for what we used to call Class 3 (High rate)\n> \n> I started with A, B,  .  . . and decided to propose more intuitive names.\n\nFor English, of course.\n\n> Unless one of you strongly objects in the next few hours, I'll have the \n> ANS announcement and AMSAT web page updated.\n\nV and S are also used for band designators, so it might get confusing \nfor an S class user on U/V, or a V class user on S2/C...\n\nCould us M for text Messaging...\n\nA, B, C, D might be easier after all!\n\nLyle\n\n",
    "attachments": []
}