Register an app on the official Stellantis Connected Vehicle API developer portal to read vehicle data and send remote commands
domain: developers.stellantis.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create an account on developers.stellantis.com and review the data catalog to see which vehicle data points (location, speed, maintenance status, doors/locks) are available per API.
Register an application to receive credentials scoped to the FCA-heritage brands (Chrysler, Dodge, Jeep, Ram, Alfa Romeo, Maserati, Fiat) that this portal covers.
Use the REST endpoints to read current vehicle data, and configure HTTP callbacks/webhooks where supported instead of polling for state changes.
Implement remote-command endpoints (e.g., horn/lights, remote start where supported) behind an explicit per-vehicle user-consent flow, since these are write actions on a real vehicle.
If your integration also needs former PSA-brand vehicles (Citroën, DS, Peugeot, Opel, Vauxhall), register separately on developer.groupe-psa.io — it is a distinct portal and API, not covered by the Stellantis Connected Vehicle API.
Known gotchas
Stellantis runs two separate developer platforms along old FCA/PSA company lines (developers.stellantis.com vs developer.groupe-psa.io); a single integration covering the full Stellantis brand portfolio needs both, not one.
Command endpoints act on a real customer vehicle — require explicit per-vehicle consent/authorization in your flow, not just app-level API credentials.
Available data fields and commands vary by brand and model year; don't assume feature parity across Jeep, Ram, and Alfa Romeo just because they're on the same portal.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?