# Best Practices for Handling SMS API Webhooks in Salesforce

**URL:** <https://devforum.zoom.us/t/best-practices-for-handling-sms-api-webhooks-in-salesforce/141412>\
**Category:** API and Webhooks\
**Tags:** api\
**Created:** [January 21, 2026, 3:09pm UTC](https://devforum.zoom.us/t/best-practices-for-handling-sms-api-webhooks-in-salesforce/141412 "2026-01-21T15:09:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![messageblink](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/messageblink/32/73243_2.png) [@messageblink](https://devforum.zoom.us/u/messageblink)\
**Post date:** [January 21, 2026, 3:09pm UTC](https://devforum.zoom.us/t/best-practices-for-handling-sms-api-webhooks-in-salesforce/141412/1 "2026-01-21T15:09:27Z")

</div>

We’re implementing API webhooks to capture SMS delivery status and inbound replies in Salesforce.

We’re currently working with Zoom SMS webhooks and reviewing other Salesforce-native apps like Message Blink to understand common webhook patterns.

Our goal is to reliably handle events such as sent, delivered, failed, and inbound messages, and map them back to the correct Lead/Contact records in Salesforce.

How are others handling webhook retries, logging, and error handling at scale?

---

<div class="post-metadata">

**Author:** ![jmendioroz](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jmendioroz/32/73988_2.png) [@jmendioroz](https://devforum.zoom.us/u/jmendioroz)\
**Post date:** [March 16, 2026, 6:57pm UTC](https://devforum.zoom.us/t/best-practices-for-handling-sms-api-webhooks-in-salesforce/141412/2 "2026-03-16T18:57:58Z")

</div>

Hey David,

Here’s how I would:

Accept the webhook exposing Apex endpoint to **only** validate and store the payload  
Save events to a Webhook Log object with a unique event ID  
and then use “ **Queueable Apex** ” to handle further processing

**Do you have Zoom CTI installed (Zoom Lightning app) in Salesforce?**
