| name | smartcar-webhooks |
| description | Receive and verify Smartcar webhooks. Use when setting up Smartcar webhook handlers, debugging SC-Signature verification, responding to the VERIFY challenge, or handling vehicle events like VEHICLE_STATE and VEHICLE_ERROR.
|
| license | MIT |
| metadata | {"author":"hookdeck","version":"0.1.0","repository":"https://github.com/hookdeck/webhook-skills"} |
Smartcar Webhooks
When to Use This Skill
- How do I receive Smartcar webhooks?
- How do I verify the Smartcar
SC-Signature header?
- How do I respond to the Smartcar
VERIFY challenge so my webhook activates?
- How do I handle
VEHICLE_STATE and VEHICLE_ERROR events?
- Why is my Smartcar webhook signature verification failing?
Verification (core)
Smartcar signs every webhook with a hex-encoded HMAC-SHA256 of the raw
request body, keyed with your Application Management Token (AMT, from the
Smartcar Dashboard), in the SC-Signature header. On setup Smartcar also POSTs
a one-time VERIFY event whose data.challenge you must hash with the same AMT
and echo back within 15 seconds — otherwise the webhook never activates. This is
Smartcar's own scheme, not the Standard Webhooks spec.
The official SDKs expose two helpers: / (hex HMAC
of any string) and / (compares the header against
the body's HMAC).