- Ya
- 5 Agosti 2026, 18:03 UTC
- Mwandishi
- Kamo
- Ahadi ya
- ee677b2
GET **************** returns one date-ordered page across notes, calls, voicemails, texts, e-mails and chat; ?channel= narrows it. Three sources are merged. Calls, voicemails, texts and e-mails come from the LEAD_COMMUNICATIONS associations; notes and chat are read directly from the lead's media stream and social session, because both are already lead-keyed — mirroring them would have added a dual-write consistency problem and, with no back-fill, lost every note and chat message that already exists. Paging is keyset, not offset. Offset across merged sources is wrong past page one: how many rows each source contributes varies, so "skip 25" does not land on strictly older, so every page costs the same and nothing is skipped or repeated even when several entries share a timestamp. Authorisation mirrors the lead-detail gate exactly, and has to — an entry is largely the lead's own contact value plus the content exchanged, so a caller without VIEW_LEAD_CONTACT_INFO_OTHERS on someone else's lead must not be able to read off this endpoint what the masked lead view withholds. Denials are audited, not just successes. The e-mail body endpoint resolves the mailbox from the association rather than from the caller: lead mail is org-wide, so the message often lives in a colleague's mailbox, and UIDs are unique only within a folder — a browser-driven fetch would silently return an unrelated message from the viewer's own mailbox. MediaAssetUrls extracts the avatar/image URL builders that were private to MediaStreamController, so a post author renders identically in the Notes tab and the All tab.