- An access token, obtained with the OAuth 2.0 Client Credentials flow. Tokens are valid for one hour and there is no refresh token. Request a new one when it expires. See API Authentication.
- A user ID (
sc-user-id), captured from the Connect redirect. Signal reads and commands require it.
Moving an existing v2 integration off per-vehicle tokens? See the Migration Guide for the phased rollout, database schema changes, and rollback plan.
Get an access token
Retrieve vehicle data
Read all signals for a vehicle withGET /vehicles/{vehicleId}/signals. For a single signal, use GET /vehicles/{vehicleId}/signals/{signalCode}.
Issue a command
Commands arePOST /vehicles/{vehicleId}/commands/..., for example security/lock, security/unlock, charge/start, charge/stop, charge/set-limit, and navigation/set-destination. Commands that take parameters send them as a JSON body. Locking a vehicle takes no body.
Verify a webhook signature
Every webhook carries anSC-Signature header with an HMAC-SHA256 of the raw body, keyed by your Application Management Token. Verify it before processing the payload. Full per-language examples are in Payload Verification, and initial endpoint setup is in Callback URI Verification.
Next steps
API Authentication
Set up client credentials and obtain access tokens.
Payload Verification
Verify webhook signatures without an SDK.

