Show an email

GET /hyperkitty/api/list/[email protected]/email/PSCYJV4EIIFFPAAR2FSXWLXXWLEY63DG/?format=api
HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/PSCYJV4EIIFFPAAR2FSXWLXXWLEY63DG/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "CA+QL-dDb6TMaJFThvwEYrp2ge4oEb82+Kad-dDCYuMCiZ1tntQ@mail.gmail.com",
    "message_id_hash": "PSCYJV4EIIFFPAAR2FSXWLXXWLEY63DG",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/PSCYJV4EIIFFPAAR2FSXWLXXWLEY63DG/?format=api",
    "sender": {
        "address": "fgeraci14 (a) gmail.com",
        "mailman_id": "300192099ab84eb799e61fb27916fdfb",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/300192099ab84eb799e61fb27916fdfb/emails/?format=api"
    },
    "sender_name": "Francis Geraci",
    "subject": "[amsat-bb] Tracking errors with HRD Sat tracking",
    "date": "2018-02-05T17:05:20Z",
    "parent": null,
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/MITAKRP42YGWAAR62MH2FXK3PD5WTOD2/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "I have noticed mention about issues with HRD Sat tracking. No \"specific\"\nproblems were mentioned  I have used HRD for may years, and know it pretty\nwell.\nAfter the last few \"updates\", an upcoming sat pass in HRD, the pass over my\nQTH, is about 5 - 10 minutes later.\nI, also run SatPC32 at the same time, along with pass predictions from\nother Web sites. All of the predictions agree, except for HRD, reporting\nthe pass later. I have missed many passes using HRD.\nWhen I switched to SatPC32, I started hearing passes.\nMy \"keps\" are current, QTH is correct, time is correct, and all the\n\"personal\" information is correct in the HRD Logbook. I am \"totally\"\nstumped.\nBest toAll\nWB1FXX\n",
    "attachments": []
}