Bouncie API

Name: Bouncie API API
Brand: Bouncie API
Availability: InStock

★ Only Publicly Available SpecIOTDevice Managementoauth223 EndpointsREST

For Agents

Read user, vehicle, and trip data for Bouncie-connected vehicles, manage application geo-zones, and subscribe to webhook events for trip and vehicle health changes.

Quickstart

Get started with Bouncie API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"search vehicle trips for a connected car"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Bouncie API API.

Retrieve the authenticated user profile and the vehicles linked to their Bouncie account

Search trip records for a vehicle, including start and end times, distance, and route metrics

Subscribe to webhooks for trip start, trip end, trip data, MIL, and low-battery events

Create application geo-zones that trigger events when a vehicle enters or exits a defined area

GET STARTED

Start building with Bouncie API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for Bouncie API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Bouncie API, keeping it validated and agent-ready. The Bouncie API gives connected-vehicle applications access to user, vehicle, and trip data for any driver who has paired a Bouncie OBD-II device. It exposes both REST endpoints for pulling data on demand and webhook subscriptions that push events such as trip start, trip end, MIL alerts, and low battery in real time. Geo-zone management endpoints let you create application-defined zones that fire programmatic events without surfacing in the user-facing Bouncie app.

Use Cases

Patterns agents use Bouncie API API for, with concrete tasks.

★ Fleet Trip Auditing

Pull every trip a vehicle has taken to build mileage logs, fuel reimbursement reports, or driver behaviour scores. The agent calls GET /v1/trips with vehicle and date filters, then aggregates distance, duration, and gps points per trip. This avoids manual odometer reads and gives accountants a defensible audit trail for tax reporting.

Call GET /v1/trips for a specific vehicle in the last week and total the distance and duration, then write the totals to a Google Sheet.

Geo-Zone Enter/Exit Automation

Trigger downstream automations when a vehicle enters or leaves a defined area such as a depot, customer site, or service zone. The agent first POSTs a location to /v1/locations/, optionally posts a /v1/schedules/, then creates the geo-zone via /v1/application-geozones/. Bouncie pushes Application Geo-Zone webhooks to your endpoint as soon as the vehicle crosses the boundary.

Call POST /v1/locations/ with depot coordinates, then POST /v1/application-geozones/ referencing the new location ID to start receiving enter and exit events.

Vehicle Health Alerting

Surface MIL (check-engine) and low-battery events to a maintenance ticketing system. Register a webhook via POST /v1/webhooks for the mil and battery event types, and Bouncie POSTs a JSON payload with the vehicle ID and event details when a fault occurs. The agent can open a service ticket automatically before the driver notices the dashboard light.

Call POST /v1/webhooks with eventType='mil' and a callback URL that creates a maintenance ticket when triggered.

Agent-Driven Vehicle Lookups via Jentic

Connect Bouncie to an AI agent through Jentic so a dispatcher can ask 'where has van 3 been today?' in chat. The agent searches Jentic for the right Bouncie operation, loads the input schema, and runs the call with the OAuth access token kept in the Jentic vault. Tokens are scoped per user, so the agent never sees the raw OAuth client secret.

Use the Jentic Python SDK to search for 'search vehicle trips', load the GET /v1/trips operation, and execute it for the dispatcher's selected vehicle ID.

Key Endpoints

23 endpoints — jentic publishes the only available openapi specification for bouncie api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v1/user

Get the authenticated user profile

GET

/v1/vehicles

Search vehicles linked to the user

GET

/v1/trips

Search trips for a vehicle

POST

/v1/webhooks

Create a webhook subscription

DELETE

/v1/webhooks/{webhookId}

Delete a webhook

POST

/v1/application-geozones/

Create an application geo-zone

POST

/v1/locations/

Create a location used by geo-zones

GET

/v1/user

Get the authenticated user profile

GET

/v1/vehicles

Search vehicles linked to the user

GET

/v1/trips

Search trips for a vehicle

POST

/v1/webhooks

Create a webhook subscription

DELETE

/v1/webhooks/{webhookId}

Delete a webhook

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Bouncie OAuth client secret and per-user access and refresh tokens are stored encrypted in the Jentic vault. Agents receive scoped tokens, so client secrets never appear in prompts, model context, or logs.

Intent-based discovery

Agents search Jentic by intent (e.g. 'search vehicle trips' or 'create application geo-zone') and Jentic returns the matching Bouncie operation with its input schema, so the agent can call the right endpoint without reading the markdown developer docs.

Time to first call

Direct Bouncie integration: 1-2 days to implement OAuth code-exchange, token refresh, and webhook signature verification. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Samsara

Enterprise telematics platform with vehicle, driver, and dashcam APIs for larger fleets.

Choose Samsara when the agent needs commercial-grade fleet telematics, ELD compliance, or dashcam video access.

Alternative

Verizon Connect Networkfleet

Verizon-backed fleet telematics API with vehicle tracking and diagnostics.

Choose Networkfleet when the agent needs Verizon-grade coverage or commercial fleet support contracts.

Complementary

OpenWeatherMap

Adds weather conditions for trip start/end coordinates returned by Bouncie.

Use alongside Bouncie when the agent needs to correlate vehicle behaviour with weather along the route.

FAQs

Specific to using Bouncie API API through Jentic.

Why is there no official OpenAPI spec for Bouncie API?

Bouncie does not publish a downloadable OpenAPI specification, only HTML reference docs. Jentic generates and maintains this spec so that AI agents and developers can call Bouncie API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Bouncie API use?

The API uses OAuth 2.0 authorisation code flow with optional PKCE. Your application is registered on the Bouncie Developer Portal, the user authorises through https://auth.bouncie.com/dialog/authorize, and you exchange the code for an access token at https://auth.bouncie.com/oauth/token. The token is sent in the Authorization header (without the Bearer prefix) on subsequent calls. Jentic keeps the OAuth client secret and per-user tokens in the encrypted vault.

Can I create a geo-zone programmatically with the Bouncie API?

Yes. Create the underlying location with POST /v1/locations/, optionally a schedule with POST /v1/schedules/, then call POST /v1/application-geozones/ referencing those IDs. Application geo-zones do not appear in the user-facing Bouncie app and only fire webhook events to your application.

What are the rate limits for the Bouncie API?

Bouncie does not publish a hard public rate limit; the API enforces fair-use throttling per application. For high-volume use cases, prefer the webhook event stream (trip data, trip start, trip end) over polling /v1/trips.

How do I receive trip events through Jentic?

Search Jentic for 'create bouncie webhook' and the POST /v1/webhooks operation is returned with its schema for eventType and url. Load the operation, then execute it with eventType set to one of tripStart, tripData, tripEnd, mil, or battery. Bouncie will POST events to your URL with an Authorization header you can verify.

Why does my call to the Bouncie API return 401 Unauthorized?

The most common causes are an expired access token (refresh it via /oauth/token with grant_type='refresh_token'), an Authorization header that includes the 'Bearer' prefix (Bouncie expects only the token value), or a user who has revoked access in the developer portal. Jentic refreshes tokens automatically when running operations through the SDK.