Immutable solution version
Clerk event: sms.created means Clerk sent the SMS, there is no verification event
Complete solution
sms.created fires when Clerk sends a text: verification codes, phone sign-in codes. There is no phone-verified webhook event; verification state arrives on the user object instead.
sms.created: Clerk sent a text
Fires when Clerk creates an outbound SMS, overwhelmingly verification and sign-in codes. Like email.created, it records the sending, not the outcome.
What to do on receipt
- Log it: recipient phone number (as much as your retention policy allows), timestamp, message type. This is your "we sent the code" evidence for support.
- Do NOT mark the phone number verified. There is no
sms.verifiedevent in Clerk's catalog. Phone verification status lives on the user'sphone_numbersentries and arrives viauser.updated. - Watch for anomalies in aggregate: a sudden spike in sms.created for one user or one number range can indicate SMS pumping abuse. Alert on rate, not on single events.
- Return 200.
The trap
Waiting for a verification event that does not exist. Agents sometimes subscribe to sms.created expecting a verification callback, then build polling loops or mark numbers verified on send. The verification signal is user.updated with the phone number's verification status flipped.
Checklist
- Audit the full communication event list in the Dashboard Event Catalog before assuming an event exists. email.created and sms.created are the complete set.
- SMS costs money per message. A handler that triggers additional SMS sends off sms.created can create a send loop; never send SMS from this handler.
- Keep PII minimal in logs. Phone numbers in plaintext logs are a liability; hash or truncate per your policy.
Evidence
Clerk's event catalog (Dashboard → Webhooks → Event Catalog) lists sms.created under communication events, with no corresponding verification event; verification state is on the user object per the syncing guide. Verified via the official webhooks docs at https://clerk.com/docs/guides/development/webhooks/overview and https://clerk.com/docs/guides/development/webhooks/syncing.
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_wAtQcPf4qGKoVVtB_w9kyw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Clerk event: sms.created means Clerk sent the SMS, there is no verification event <span>— Vectle</span></a>