Platform · Developers
Wire vehicle intelligence into your stack
We're building Unbroken Car toward a documented REST API and webhooks: push vehicle and fleet data in, pull schedules and renewals out, and stay in sync with the telematics, ERP, and insurance systems you already run. None of it is live yet. This page is the plan, and early conversations shape it.
What we plan to connect
The API is being designed to sit alongside your existing systems, not replace them. Everything below is planned, except where marked live.
Telematics
Planned: stream mileage and usage from your telematics provider so maintenance schedules stay current without manual updates.
ERP & operations
Planned: sync vehicle records and maintenance events with the ERP or fleet system your operations already depend on.
Insurers
Planned: share the vehicle and renewal data insurers need through a controlled, permissioned connection.
Vehicle registry
Live today: official Israeli plate lookup with a daily registry sync, so vehicle details and renewals populate automatically.
Webhooks
Planned: subscribe to events (schedule updates, upcoming renewals) and push them anywhere.
Data export
Planned: pull structured fleet and vehicle data out on demand for your own reporting and BI tooling.
How it's designed to work
- 1
Authenticate
You'll generate an API key for your organization and authenticate every request over HTTPS, with keys scoped to what each integration needs.
- 2
Call the endpoints
Clean REST endpoints will let you add vehicles, read schedules and renewals, and post mileage or service events as they happen.
- 3
Subscribe to webhooks
You'll register webhook URLs and Unbroken Car will push events to you as they happen: no polling, no missed updates.
- 4
Stay in sync
As vehicles move and data changes, your systems and Unbroken Car will stay aligned automatically, in both directions.
Developer experience
A clean, predictable surface
JSON in, JSON out, over plain HTTPS. The shapes below are a design sketch of the API we're building, not live endpoints. The real API will be documented endpoint by endpoint.
GET /v1/vehicles/{id}/health\nAuthorization: Bearer sk_live_…{ "vehicleId": "…", "healthScore": 82, "confidence": "moderate", "recommendations": [ … ] }{ "event": "recommendation.created", "vehicleId": "…", "urgency": "likely" }Developer FAQ
Is the API REST or GraphQL?+
The plan is a documented REST API with predictable JSON request and response bodies over HTTPS, plus webhooks for event-driven updates. It isn't live yet.
How does authentication work?+
The design: organization API keys sent as bearer tokens, scoped and rotatable, with all traffic encrypted in transit. Details will be published with the API.
Do you support real-time updates?+
Not yet. Webhooks for events like schedule updates and upcoming renewals are on our roadmap, so you won't have to poll for changes.
Can I connect my existing telematics and ERP?+
Not today, but that's exactly what we're designing toward. If you run a specific stack, telling us about it now helps us prioritize what to build first.
Who do I talk to about an integration?+
Reach out and our team will walk through your stack and where it fits on the roadmap. Early conversations directly shape what we ship first.
Help us design your integration
Tell us what you run and we'll map where it fits on the roadmap. Early partners shape the endpoints and webhooks we build first.