Handle inbound MMS webhook (Sinch)
Inbound webhook called by the Sinch MMS JSON API when an MMS is delivered to a Tether-provisioned number. Acknowledges within 10 seconds and processes asynchronously: media is downloaded and re-uploaded to R2, then the message is appended to the contact’s conversation.
Body
Sinch-assigned MMS message id; echoed back in the ack for log correlation.
Sinch traffic direction marker — MMS_MO for inbound (mobile-originated) MMS.
Sender phone number in E.164.
Tether-provisioned recipient number that received the MMS.
Optional text content sent alongside the media.
Attached media items. Each is downloaded from Sinch and re-uploaded to R2 before persistence.