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/7EYQQ4WOUP6KLXJS55RGKXICRHNTJP7Y/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "7EYQQ4WOUP6KLXJS55RGKXICRHNTJP7Y",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/T5VH2HBM44A4SMERZFCZASIU5X7WWZ3R/?format=api",
    "sender": {
        "address": "w0jab (a) big-river.net",
        "mailman_id": "8b32873ea9a7498c995a03de2a8227b3",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/8b32873ea9a7498c995a03de2a8227b3/emails/?format=api"
    },
    "sender_name": "John Becker",
    "subject": "[amsat-bb] Re: The Need for Phonetics",
    "date": "2011-04-11T16:16:12Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/TJAZNDLQDOLJZSSRSMSMDSMJ5QXYQ5VJ/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "At 07:52 PM 4/10/2011, you wrote:\n>This is a bunch of baloney!  Your \"unpublished\" non-standard just confuses \n>most people.  I've listened to hours of DX and the ITU alphabet gets through \n>just fine.  It's when people start throwing out their cutesy made up \n>alphabet that it gets confusing.\n\nI could not agree more.\n\nover the years I think I have heard it all.\nBut nothing and I due mean nothing works like\nthe old standard. \n\nIt's confusing enough living in a town named \"LOUISIANA\"\nin the state of \" MISSOURI.\n\nJohn, W0JAB\n\n\n\n\n",
    "attachments": []
}