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/2URP2LHEZZZ2SUUTUDMSPCK56D55JCSD/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "2URP2LHEZZZ2SUUTUDMSPCK56D55JCSD",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/AMAQRI5GKDPRC44SWWBORWSQKIP7SODK/",
    "sender": {
        "address": "red (a) redwilloughby.com",
        "mailman_id": "9091480b0f0242c6abfaf7ea45dbf3e1",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/9091480b0f0242c6abfaf7ea45dbf3e1/emails/"
    },
    "sender_name": "Red Willoughby",
    "subject": "Re: [amsat-bb] PSAT PSK31 experimental software",
    "date": "2015-07-17T22:50:52Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/Y2HZ5N35VWXJ2MEILTEXDCDR5UPPYSIW/",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Thanks for resolving that, Dave. Now HRD SatTrack has only one instance \nof NO-84 and one instance of NO-83 and their AOS times seem to correlate \nwith SatPC32.\n\nI am still not certain when to look for NO-83. Maybe WB4APR can update \nus on where BRICSAT is relative to PSAT when he has time. I would like \nto continue trying to transpond through this amateur space asset.\n\nThanks,\n\nRed\nKC4LE\n\n",
    "attachments": []
}