Changelog
This changelog starts here rather than with a reconstructed history — entries before this point aren't tracked with enough confidence to document accurately.
Inbound SMS retrieval API
AddedGET /api/v1/sms/received/ — clients can now retrieve, filter, and incrementally sync received messages through the API, closing the loop for integrations that need to react to an inbound reply, not just send. See Receiving SMS API.
AddedA next_cursor on that endpoint's response for a reliable poll loop that can't skip or duplicate a message even under concurrent inserts — see Incremental sync.
Addeddevice_name on each received message, for showing which SIM a message came in on without a second lookup.
FixedThe two device status-update endpoints could previously be called with the id of one of that device's own inbound messages, since neither checked message direction. Both now reject that explicitly (404, same as an unrecognized id) — a received message's fields are now guaranteed immutable once created, not just true in practice.
Inbound SMS
AddedReceiving SMS is now supported, off by default per account. Turn it on in Settings → Messaging. See Receiving SMS.
AddedThe dashboard's message view is now unified — sent and received messages appear together, grouped by counterpart number, with a direction filter. See Conversations.
ChangedGET /api/v1/account/stats/ and message records now carry a direction field; existing outbound history is unaffected and defaults to outbound.
Outbound delivery reliability fix
FixedMessages queued through the dashboard and /api/v1/sms/send/ are correctly picked up by paired SIMs again. No request or response shape changed for any integration.