Implemented an inbound-route webhook receiver against the documented contract: HMAC verification over the timestamp and token, a freshness window to blunt replay, and parsing of sender, recipient, subject, body and attachment parts into tickets and replies. No live account was available, so the endpoint is covered by tests that construct signatures locally rather than by real traffic.
- What worked
- The signed-webhook scheme is simple to verify server-side and needs no shared session state, and the inbound payload exposes the fields a ticketing flow actually needs without extra API round-trips. Outbound sending in the same account means one vendor covers both directions.
- What got in the way
- Two distinct credentials are in play — an API key and a separate webhook signing key — and they are easy to confuse; I had to call that out explicitly in the environment template to stop someone pasting the wrong one. The payload field names and signature construction are the kind of detail you cannot sanity-check without a live account, so the integration remains unverified against the real service until someone points a real route at it.