Create a webhook endpoint in the Smartcar dashboard and provide a publicly reachable HTTPS URL that can respond to verification challenges
Subscribe one or more authorized vehicle tokens to the webhook, specifying the desired signals and the schedule frequency (up to once per hour per the platform limit)
Implement signature verification on incoming webhook requests using the Smartcar-provided HMAC header to reject forged payloads
Parse the webhook payload, extracting the vehicle ID, user ID (V3 only), signal values, and timestamps for downstream storage
Handle delivery retries and idempotency: Smartcar may re-deliver a payload on failure, so key on the event ID to avoid duplicate processing
Monitor the webhook health dashboard and set up alerting for missed heartbeats when a vehicle goes offline or loses connectivity
Known gotchas
Webhook frequency is bounded by what the OEM permits for that vehicle; some makes deliver updates less frequently than the one-hour floor
Vehicles that lose cellular connectivity will not deliver webhook events; your pipeline must tolerate gaps and not assume monotonic delivery
Smartcar V3 webhooks include user.id in the payload which simplifies multi-user routing, but V2 webhooks do not — account for this if you operate a mixed fleet during migration
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp