canonical: https://jentic.com/apis/api.bouncie.dev/bouncie

# Bouncie API

The Bouncie API provides connected-vehicle telematics for cars fitted with a Bouncie device. It lists vehicles and the authenticated user and returns trips with location and driving data. Beyond reading vehicle data, it manages webhook subscriptions for real-time events, application and user geozones, saved locations, and schedules. Read and write operations let an agent both monitor a vehicle and configure the alerts and automations around it.

## For AI agents

List connected vehicles, read trips with GPS and driving data, manage webhooks and geozones, and configure locations and schedules for Bouncie devices.

## Scope

Covers Bouncie connected-vehicle data and its geozone, webhook, location, and schedule configuration. Does not control the vehicle or cover cars without a Bouncie device.

## Capabilities

- List connected vehicles and the authenticated user
- Retrieve trips with location and driving data
- Create, update, and delete webhook subscriptions
- Manage application and user geozones
- Create, update, and delete saved locations
- Create, update, and delete schedules

## Use cases

### Vehicle Trip Monitoring

A fleet or personal-tracking agent reads trips for connected vehicles to summarize mileage and driving behavior. It lists the vehicles, then retrieves their trips with location and driving data. Through Jentic the agent finds the trips operation and calls it with its OAuth token managed for it.

Example prompt: List connected vehicles and retrieve their recent trips with location data

### Geozone Entry and Exit Alerts

A safety agent sets up geozones and is notified when a vehicle enters or leaves them. It creates the geozones and a webhook subscription so events are pushed as they happen. This backs curfew or worksite alerts without polling.

Example prompt: Create a geozone and a webhook so the agent is notified on entry and exit events

### Event-Driven Vehicle Automations

An automation agent subscribes to Bouncie webhooks to react to vehicle events in real time. It creates, updates, and removes webhook subscriptions as its automations change. Pushed events let downstream systems respond without repeated calls.

Example prompt: Create a webhook subscription for vehicle events and update it as automations change

### Location and Schedule Management

An agent maintains saved locations and schedules tied to a vehicle account. It creates, updates, and deletes locations and schedules to keep configurations current. This supports reminders and place-based logic in a connected-car app.

Example prompt: Create a saved location and a schedule, then update them as the account changes

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/vehicles` | List connected vehicles |
| GET | `/v1/trips` | Retrieve trips with location and driving data |
| GET | `/v1/user` | Get the authenticated user |
| POST | `/v1/webhooks` | Create a webhook subscription |
| GET | `/v1/application-geozones/` | List application geozones |
| POST | `/v1/locations/` | Create a saved location |
| GET | `/v1/schedules/` | List schedules |

## Key resources

- **Vehicles** — Connected vehicles and the authenticated user
- **Trips** — Trips with location and driving data
- **Webhooks** — Subscriptions for real-time vehicle events
- **Geozones** — Application and user geozones for location alerts
- **Locations and schedules** — Saved locations and schedules tied to the account

## Why Jentic

- **Setup:** Wiring Bouncie by hand means running its OAuth 2.0 flow against api.bouncie.dev, refreshing the token, and threading it through every trips and webhook call yourself. Through Jentic you install once, import Bouncie from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Bouncie mixes read and write operations, so a rule limits your agent to the operations it needs, such as listing vehicles and reading trips. You choose which operations it may call, so creating webhooks, geozones, or schedules is included only when you add it.
- **Credential handling:** Your Bouncie OAuth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'retrieve vehicle trips' or 'create a geozone', and Jentic returns the matching Bouncie operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Smartcar** — Smartcar reads vehicle data directly from many car brands without a hardware device, an alternative to Bouncie.
- **Samsara** — Samsara offers commercial fleet telematics and safety hardware, an alternative aimed at larger fleets.
- **Telematics SDK** — Telematics SDK collects driving data from mobile devices, an alternative that needs no in-car hardware.
- **Particle** — Particle is a general IoT device platform; pair it with Bouncie to combine vehicle data with other connected sensors.

## FAQ

### What authentication does the Bouncie API use?

The Bouncie API authenticates with OAuth 2.0, and the resulting access token is sent in the Authorization header. Through Jentic, that token is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's prompt or logs.

### What vehicle data can the Bouncie API return?

The Bouncie API lists connected vehicles and returns trips with location and driving data. An agent can list the vehicles on an account and then retrieve their trips to summarize mileage, routes, and driving behavior.

### Can I receive real-time vehicle events from the Bouncie API?

Yes. The Bouncie API supports webhook subscriptions, so an agent can create a webhook and receive vehicle events, including geozone entry and exit, as they happen. Subscriptions can be updated or removed as your automations change.

### What are the rate limits for the Bouncie API?

The OpenAPI spec does not specify rate limits for the Bouncie API. Check the Bouncie developer documentation at https://docs.bouncie.dev for current limits, and back off when you receive a 429 response.

### How do I read vehicle trips through Jentic?

Search Jentic for 'retrieve vehicle trips', import Bouncie from the API Directory, and store your OAuth credentials once. Jentic returns the trips operation with its parameters so your agent can call it directly. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit what my agent is allowed to do with the Bouncie API?

Yes. You write a rule that allows only the operations the agent needs, such as listing vehicles and reading trips, so writing webhooks, geozones, or schedules stays out of reach unless you add it. Because Jentic One is self-hosted, those rules and the audit log of every call stay on your own infrastructure.

### Is there a Bouncie API MCP server?

You do not need an MCP server to give your agent the Bouncie API. Jentic connects it directly from the API Directory: import it, store your credentials once, and your agent can read trips and manage webhooks and geozones. That also keeps your agent's context free of an extra server's tool definitions.