جارٍ التحميل
Developer access
Integration points are being prepared carefully.
The public API is not generally available yet. Early partners can discuss garage, supplier, and fleet integrations without relying on fake endpoints.
API posture
Public API documentation is planned, but not live.
Integration work will preserve repair-case access controls, supplier/customer finance boundaries, and audited status changes.
Webhook and sync examples below are roadmap targets, not production endpoints.
What the integration layer should enable.
These capabilities are intentionally scoped around implemented repair workflows and privacy boundaries.
Supplier inventory sync
A future integration path for suppliers to respond to structured garage part requests from their own systems.
- Stock-aware responses
- PO-linked updates
- No customer-facing supplier notes
Garage system bridge
Planned sync points for repair cases, estimates, invoices, and status changes from existing garage software.
- Case status events
- Estimate context
- Invoice amount-due records
Fleet workflow export
A future route for fleet platforms to consume repair status and downtime context without fake telematics.
- Vehicle repair state
- Downtime checkpoints
- Cost approval context
Event examples for future integrations.
| Event | Trigger | Payload includes |
|---|---|---|
| case.status_changed | Repair case status updates | Case id, status, vehicle, garage |
| estimate.sent | Garage sends estimate to customer | Estimate id, case id, amount due |
| estimate.approved | Verified customer approves estimate | Estimate id, case id, approval timestamp |
| po.accepted | Supplier accepts purchase order | PO id, supplier id, ETA |
| po.received | Garage confirms received parts | PO id, received timestamp, safe part context |
| invoice.issued | Garage issues customer invoice | Invoice id, case id, amount due |