Menu

Zero-Disk Webhook Normalization: Stopping ServiceTitan v2 Schema Rejects & Retry Storms in 0.05ms
πŸ“°

Zero-Disk Webhook Normalization: Stopping ServiceTitan v2 Schema Rejects & Retry Storms in 0.05ms

DEV Community: typescriptΒ·KallowayThayerΒ·5 days ago
#9ZmPDw0M
#devtotypescript#devto#dev#call#digits
Reading 0:00
15s threshold

Last week I wrote about handling HTTP 429 burst lockouts and OAuth token stampedes when piping high-volume lead traffic into ServiceTitan v2.

Rate limiting solves the transport bottleneck, but it does nothing for the actual payload errors that quietly kill 6% to 9% of paid Google LSA, Meta, and aggregator leads before dispatch ever sees them.

If you manage webhook infrastructure for multi-branch HVAC, plumbing, or roofing fleets, you have probably watched Zapier or Make bridges choke on three specific edge cases:

Phone Extensions Breaking E.164 Validation: A commercial facility manager types (512) 482-9104 ext. 42 (do not call after 8pm) into a form. Strict E.164 validators reject the string, or worse, strip it down to a malformed 12-digit number that fails customer lookup.

Webhook Retry Storms Creating Duplicate Jobs: When an upstream webhook sender times out, it fires the same payload three times with slightly mutated metadata ( retry_count: 2 or a new _delivery_timestamp_ms ).…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.