Expose SMS and email history in the API (calls are already there)
Tyler Servais
The API has no way to read SMS or email records. Calls do:
GET /v1/{clients|projects|requests}/{id}/calls works well. The other two
channels have nothing.
Verified against a live workspace on July 30 2026. All of these 404 with a
valid key:
/v1/messages, /v1/sms, /v1/texts, /v1/emails, /v1/conversations,
/v1/threads, /v1/inbox, /v1/communications
/v1/{clients|projects|requests}/{id}/messages
/v1/{clients|projects|requests}/{id}/emails
/v1/{clients|projects|requests}/{id}/sms
The only communications webhook is CALL_UPSERTED, and CSV export covers
Projects, Clients, and Requests only. Net: zero SMS and zero email records
reachable by any supported method. Anything sent through Coperniq on those
two channels can't be read back out.
What this blocks: a unified customer timeline (an engineer walking into a
consultation can't pull the full history), response-time and touch-count
reporting on the pipeline, and any durable copy of customer communications
outside the platform.
Requested solution: mirror the calls pattern on the other two channels.
GET /v1/{clients|projects|requests}/{id}/messages and .../emails, paginated
like the other list endpoints.
Interim: including communications in CSV export would unblock most of this
immediately, if the endpoints are a longer build.
Later: MESSAGE_RECEIVED and EMAIL_RECEIVED webhooks alongside the existing
CALL_UPSERTED would make real-time mirroring possible.