canonical: https://jentic.com/apis/stellantis.com/stellantis

# Stellantis Connected Vehicle API

Stellantis Connected Vehicle API for account management, authentication, remote vehicle control, telemetry data, and trip information. The API exposes 10 endpoints.

## For AI agents

Programmatically get account info, register account. Covers 10 operations.

## Scope

Does not handle payments, communications, or crm - use for iot and hardware only.

## Capabilities

- Get account info
- Register account
- Link account
- Unlink account
- Set password
- Reset password
- Delete account

## Use cases

### IoT and Hardware Operations

Use the Stellantis Connected Vehicle API to perform iot operations programmatically. The API provides 10 endpoints covering core functionality including get account info, register account, link account.

Example prompt: Call GET `/v1/account` to get account info

### Automated Account Management

Automate account operations by combining multiple Stellantis Connected Vehicle API endpoints. Agents can register account and then link account in a single workflow.

Example prompt: Call POST `/v1/account/register` to register account, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Stellantis Connected Vehicle API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'get account info', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/account` | Get account info |
| POST | `/v1/account/register` | Register account |
| POST | `/v1/account/link` | Link account |
| POST | `/v1/account/unlink` | Unlink account |
| POST | `/v1/account/setpassword` | Set password |
| POST | `/v1/account/resetpassword` | Reset password |
| POST | `/v1/account/delete` | Delete account |
| POST | `/v1/auth/token` | Get auth token |

## Key resources

- **Account** — Operations related to Account
- **Authentication** — Operations related to Authentication
- **Remote Control** — Operations related to Remote Control
- **Vehicle Data** — Operations related to Vehicle Data

## Why Jentic

- **Setup:** Wiring the Stellantis Connected Vehicle API by hand means obtaining a bearer token from its `/v1/auth/token` endpoint, sending it on every call to api.stellantis-developers.com, and tracking which vehicle each request targets yourself. Through Jentic you install once, import the Stellantis Connected Vehicle API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** This API puts the vehicle id in the URL path (`/v1/{vin}/data` and `/v1/{vin}/remote`), so a rule can pin your agent to reading data or issuing remote commands for a single vehicle. You choose the operations it may call, so account operations like unlinking or account deletion are not included unless you add them.
- **Credential handling:** Your Stellantis Connected Vehicle API token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'read connected vehicle data' or 'send a remote command to a car', and Jentic returns the matching Stellantis Connected Vehicle API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Particle** — Alternative iot API
- **Stripe** — Complementary API for broader integration workflows
- **Twilio** — Complementary API for broader integration workflows

## FAQ

### What authentication does the Stellantis Connected Vehicle API use?

The Stellantis Connected Vehicle API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get account info with the Stellantis Connected Vehicle API?

Yes. Use the GET `/v1/account` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Stellantis Connected Vehicle API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get account info through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get account info'. Jentic returns the matching Stellantis Connected Vehicle API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Stellantis Connected Vehicle API have?

The Stellantis Connected Vehicle API exposes 10 endpoints covering account, authentication, remote control operations.

### Can I limit what my agent is allowed to do with the Stellantis Connected Vehicle API?

Yes. Because you run Jentic One yourself, your own rules decide which of this API's operations and credentials the agent may use. This API carries the vehicle id in the URL path, as in `/v1/{vin}/data` and `/v1/{vin}/remote`, so you can pin the agent to reading telemetry or issuing remote commands for a single vehicle. You also pick the exact operations it may call, so account actions such as unlinking or deleting an account stay off limits unless you add them.