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/526GDIC53SSCPLKS27S3G3VFKKLBEKWS/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "526GDIC53SSCPLKS27S3G3VFKKLBEKWS",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/526GDIC53SSCPLKS27S3G3VFKKLBEKWS/?format=api",
    "sender": {
        "address": "amsat-bb (a) wd9ewk.net",
        "mailman_id": "21664df01bef4757931b7cdb42a9e768",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/21664df01bef4757931b7cdb42a9e768/emails/?format=api"
    },
    "sender_name": "Patrick STODDARD (WD9EWK/VA7EWK)",
    "subject": "[amsat-bb]  received K4T QSL today",
    "date": "2010-06-25T05:30:36Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hi!\n\nThanks to the K4T group and their QSL manager, K5WW, for the nice\nQSL card that was in the mailbox today - along with the new grid\nEL84.  Not only was the satellite operation top-notch, the way \nthe QSOs were listed on the card was perfectly done.  Each QSO is\nlisted, including the satellite and the mode (V/U or U/V) along \nwith the other standard data - and it is all printed on the card!  \nNone of the QSO data is written in, as some DXpeditions have done \nin the past to deal with satellite QSOs on their cards.  \n\n73!\n\n\n\n\n\nPatrick WD9EWK/VA7EWK\nhttp://www.wd9ewk.net/\n  \n\n\n",
    "attachments": []
}