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/FTWE6KW3CGTA46VLWF4RXOMIEX3FPOSD/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "FTWE6KW3CGTA46VLWF4RXOMIEX3FPOSD",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/XZ222TWPOJZDSVYAYCQDWTOTW2Y6FAZY/",
    "sender": {
        "address": "ai6do (a) yahoo.com",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Ryan Noguchi",
    "subject": "Re: [amsat-bb] Standard for AMSAT status board observations of FS-3",
    "date": "2018-06-02T14:47:08Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/SYTNNC6UD7VKXROL5ID25NOYTYW7D2ME/",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": " This document describes the format of the packets: https://www.amsat.org/wordpress/wp-content/uploads/2017/09/FalconSAT-3-Status-Packets.pdf\n\n\nPFS3-1 is the PATH you use for digipeating, but that call is not only used for the digipeating function. \n\n73, Ryan AI6DO\n\n    On Saturday, June 2, 2018, 5:00:24 AM PDT, Robert Switzer <[email protected]> wrote:  \n \n  PFS3-1 is the path for APRS digipeating, correct?\nI assume all the other passes displayed are from the BBS.\nIs there a list of what I would expect to see?\n73, Rob KA2CZU\n\n   \n    \n",
    "attachments": []
}