One post in full with its top comments

Frammenti di codice

curl "https://api.oanor.com/deso-api/v1/post" \
  -H "x-oanor-key: oanor_test_..."

await fetch("https://api.oanor.com/deso-api/v1/post", {
  headers: { "x-oanor-key": "oanor_test_..." }
});

$ch = curl_init("https://api.oanor.com/deso-api/v1/post");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$out = curl_exec($ch);

import requests
requests.get(
    "https://api.oanor.com/deso-api/v1/post",
    headers={"x-oanor-key": "oanor_test_..."}
)

Risposta di esempio

Una risposta reale di questo endpoint, acquisita dall'ultimo health check.

{
    "data": {
        "body": "Hi all, apologies for the issues on Focus. Everything should be resolved now. Thank you for your patience.\n\nThis was a complex technical issue with the Focus api servers that we had to put significant resources into fixing, but everything appears to be running smoothly now. The feed should update soon, and the Openfund live transaction histories should also be updating in real time again (they were powered by the same service).",
        "note": "One DeSo post in full with its engagement (likes, diamonds, comments, reposts) and its top comments. DeSo posts live on-chain, so a hash is permanent. Pass post_hash (64-hex, from /v1/posts or /v1/feed) and limit (max comments, 1-100).",
        "likes": 0,
        "author": "nader",
        "source": "DeSo",
        "reposts": 8,
        "comments": 28,
        "diamonds": 21,
        "post_hash": "d35ec22748229a8e864c402910e9ea5c4b784b505d0c461bc7e8f37a12fe9a01",
        "timestamp": "2026-06-07T06:20:48.294Z",
        "image_urls": [],
        "comment_list": [
            {
                "body": "How long till the real issues will be fixed tho?\n\nOne example, go use focus and try to send your CCv2 to some user. Cant be done.",
                "likes": 0,
                "author": "Pixelangelo",
                "reposts": 0,
                "comments": 4,
                "diamonds": 1,
                "post_hash": "c2651a86efa56c1958ceb3ae8baa7372cda0a341a6ee1f21298d367e6ece7ebb",
                "timestamp": "2026-06-07T06:52:06.842Z"
            },
            {
                "body": "The issue isn't resolved dude and I'll continue to extend the offer to help - I'm here, have always tried to help, and remain always willing.\n\nI've sent the team details repeatedly, but get ignored.\n(or worse still - dubbed as a \"FUD'er\" by your colleagues)\n\nconsumer-state.bin saved by the core repo is the issue with the missing transactions. It simply doesn't save state reliably - this is the cause of all the issues with the PDH stack.\n\nWe've confirmed this through:\n- 10 repeat syncs with high spec hardware\n- repeated repopulation of the PG database through clearing the consumer-progress and restarting syncs (always the same gaps)\n- confirmed missing txns and blocks across ALL operators running the PDH stack\n- confirmed missing txns on core infra - both Focus (openfund) and DESO-production (explorer)\n\n\nJust for transparency:\nThis isn't to FUD, but I will be detailing all of this on-chain and publicly through a forthcoming @SafetyNet community meeting. It needs to be discussed and I have tried (and tried, and tried) for well over a year to progress things with little/no response or engagement.",
                "likes": 0,
                "author": "StarGeezer",
                "reposts": 0,
                "comments": 4,
                "diamonds": 2,
                "post_hash": "576a0ae515565a008527d9e7e569a4436c27d25cb0ec7a486232326bb6c58e17",
               
…