Integrations
What connects to TyreSync, and what doesn't yet.
TyreSync is a workspace, not a walled garden: data comes in through the browser, a CSV file or a partner feed, and leaves through branded share links and exports. This page states plainly what is live, what is arranged on request, and what is still on the roadmap.
Live
Offline capture, CSV, share links
Partner API
Retread factory status, scoped
On request
Probes, odometer and telematics
Roadmap
Self-serve pairing, public API
The honest status board
Live, on request, roadmap — labelled, not implied.
Every row below is a real state, not a promise worded like a feature. "Live" ships in every workspace today. "On request" works, but is arranged per client rather than switched on yourself. "Roadmap" is not built yet; where we have no date for it, we say nothing rather than invent one.
| Integration | What it does | Status |
|---|---|---|
| Offline-first PWA capture | Surveys, stock and callouts write to the device first and sync continuously — on Android, iOS and desktop browsers alike. | Live |
| CSV export and import | Your book exports to CSV on Solo and above; vehicle lists and your shop's own tyre catalogue import the same way. | Live |
| Live share links | Reports and in-progress documents go out as hashed, revocable links that open without a login. | Live |
| Retread factory status API | A scoped, revocable interface at /api/retread/v1 lets a retread factory report casing and batch status straight back into your batches. | Live — partner access |
| Bluetooth tread-depth probes | A probe feeds tread readings into the survey position over Web Bluetooth — Android and desktop Chrome only; iOS Safari cannot pair. Assisted setup: you send us the probe, we configure it. | On request |
| Odometer and telematics feeds | Odometer readings or a telematics feed wired into the book, so kilometre figures arrive without retyping. | On request |
| Accounting hooks | Invoice and client data pushed toward your accounting package, arranged per shop. | On request |
| Self-serve probe pairing | Pair a supported probe to your own workspace without our involvement. | Roadmap |
| General public API | A documented, self-serve API surface beyond the scoped retread partner interface. | Roadmap |
Probe capture, stated plainly
Android and desktop Chrome. Not iOS. Not yet self-serve.
Bluetooth tread-depth probes work through Web Bluetooth, a browser feature that exists on Android and on desktop Chrome — and nowhere on iOS, because iOS Safari does not implement it. An iPhone or iPad runs every other part of a fleet tyre survey; probe pairing is the single exception, and manual tread-depth and pressure entry is the path there.
Setup is assisted rather than self-serve: you send us the probe, we configure the pairing against your workspace and hand it back working. Self-serve pairing is on the roadmap, not in the product today.
What "on request" means
Real capability, arranged per client.
Odometer and telematics feeds and accounting hooks are integrations we wire against your stack, not a switch you flip. The retread factory API is live code; partner access is scoped and revocable, issued per factory on request. There is no general public API and no public API documentation today — the retread partner interface is the only external surface.
Tell us the system you need connected and we will tell you honestly whether it is a project, a roadmap item or a bad fit.
Talk to us about a specific integrationKeep reading
- Fleet tyre surveysManual and probe-assisted capture, device by device.
- Casing and retread trackingThe batches the factory status API reports back into.
- PricingWhich plan carries CSV exports, share links and the rest.
- FAQ: probes, iOS, offline and your dataThe short answers to the questions we hear most.