When a customer texts you a picture, your webhook receives the message and a link to the media. Fetch the file quickly, store it in your own storage and don't rely on the provider's link staying valid. That's the whole pattern, and the rest is defensive work.

The flow

  1. A customer sends a picture to your number.
  2. Ready calls the webhook URL you set up with the message.
  3. Your endpoint acknowledges fast and queues the work.
  4. A worker downloads the media, checks it and stores it.
  5. Your app shows the message with your stored copy.

The exact payload is in the Ready docs and the messages reference. Check the docs for the media field instead of guessing names.

Acknowledge first, download second

A slow download inside the webhook handler risks timeouts and repeat deliveries. Return success quickly, then process. Our post on fast acknowledgments shows the pattern, and deduplication covers repeat deliveries.

Treat the file as untrusted

  • Check the content type against an allow list: images, and video if you want it
  • Cap file size
  • Scan or re-encode images before showing them to staff
  • Never serve it from the same domain as your app with executable types

Storage

Provider links aren't a permanent archive. Copy the file into your own bucket, key it by message id and keep the link in your database. Delete it when the contact or customer is deleted.

What MMS can and can't do

TopicNote
Sendingmedia_url on POST /v1/messages sends a picture
CostMedia segments can cost more than text
Opt-outA STOP still opts out, even in a message with a photo
PrivacyCustomers send IDs and documents, so restrict who can view them

Keep health and other sensitive content out of the workflow where you can. Ready is not HIPAA compliant.

The takeaway

Ack fast, download in a worker, store your own copy and treat the file as untrusted input. See the MMS API guide for sending and receiving SMS by webhook for the text-only case.