Backend · Messaging
URI Unified Inbox
One inbox for a business's Instagram, Messenger and WhatsApp conversations: DMs and comments in a single list, with honest delivery state rather than a hopeful tick.
Status
In progress
Role
Lead engineer
Timeline
2026
Delivery state you can act on
Most inboxes show a message as sent and leave it there. This one moves through pending, accepted, delivered and read, and says failed or unknown when that is what happened, because a reply that silently did not arrive is worse than one that visibly did not.
Eligibility is checked before the send and again at the send itself: the reply window, the channel's capability, the media type and the permission. One command produces one provider call, carrying a client idempotency key, so a retry cannot post twice.
What the tests actually cover
The suite verifies the things that go wrong in production rather than the happy path: timeouts, crashes mid-send, echo races, rate limits, token expiry, duplicate keys, and repeated webhook delivery.
It also states what it cannot verify. Behaviour against the real Meta APIs, a real DocumentDB and App Review are all outside what a test suite can prove, and the README says so rather than implying the green run covers them.
Results
- 153 tests covering webhook authenticity, ordering, the whole send pipeline and cross-workspace isolation.
- A standalone service with its own database and deployment, which imports nothing from the main backend.
- Runs with one command against an in-memory database and a sandboxed Meta, so a frontend can be built before any account is connected.
Got something like this to build?
Start a project