Catching up after a missed webhook
A webhook delivery is attempted once. If your endpoint was down, read back what you missed:- Take the
receivedAtof the last event you handled and go back five minutes — messages that arrive together can be delivered out of order. GET /api/v1/conversations?since=<that time>— every conversation a customer has written in since then, including brand-new ones.- For each,
GET /api/v1/conversations/{id}/messages?since=<same time>. - Skip any message whose
idmatches amessageIdyou already handled.
GET /conversations
Newest first.
string
whatsapp, web, telegram, voice or email.string
ISO 8601. Keeps conversations where the customer last wrote at or after this.
number
Up to 100. Default 25. Follow
nextCursor with ?cursor= for the next page.GET /conversations/{id}/messages
Newest first. The customer’s messages, your agent’s replies, and replies a
teammate sent from the inbox (author: "teammate"). Your team’s internal notes
are not included.
string
ISO 8601. Keeps messages written after this.
number
Up to 100. Default 25. Follow
nextCursor with ?cursor=.