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/KEEMEIB7QDYFNTVZQA3ZNLITH5CNAN4F/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "KEEMEIB7QDYFNTVZQA3ZNLITH5CNAN4F",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/O3IGI32LY4SVQOWNSPDQ6CJC4RMULM2L/?format=api",
    "sender": {
        "address": "contact (a) juliennicolas.com",
        "mailman_id": "99a5052c42c04892885a9656c8e7b17d",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/99a5052c42c04892885a9656c8e7b17d/emails/?format=api"
    },
    "sender_name": "Julien NICOLAS",
    "subject": "Re: [amsat-bb] A new 400bps telemetry beacon now on!",
    "date": "2019-02-13T23:05:02Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/JWMT2QRSL67R6M5MLFHJKYENGB72EHQR/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "> Also, I noticed that the timestamp inside decoded data wasn't correct.\n> It seems to think that we are the 2000-07-30.\n\nIt's a local issue from wine, because there is no timestamp in the \nbeacon.\n",
    "attachments": []
}