RideWrench developer platform
Connect the systems your fleet already runs.
Bring ELD, telematics, TMS, DVIR, and internal operations data into one service workflow, without replacing your source systems.Fleet-owned access
Every key belongs to one approved fleet tenant and can be revoked independently.
Least privilege by default
Read and write scopes keep ELD ingestion separate from operational control.
Safe retries
Idempotency keys make event and record creation repeatable without duplicates.
REST API
A practical fleet operations surface.
Use cursor pagination for large fleets. Every response carries request and rate-limit identifiers for support and observability.GET /api/v1/fleetFleet identity and authorityGET · POST · PATCH /api/v1/equipmentMixed fleet assets and telematics stateGET · POST · PATCH /api/v1/breakdownsRoadside eventsGET · POST · PATCH /api/v1/maintenancePlanned workGET · PATCH /api/v1/work-ordersProvider service lifecycleGET /api/v1/dvirInspection history
curl https://www.ridewrench.com/api/v1/events \
-H "Authorization: Bearer rw_live_..." \
-H "Idempotency-Key: eld-fault-184921" \
-H "Content-Type: application/json" \
-d '{
"type": "vehicle.fault.detected",
"externalId": "fault-184921",
"occurredAt": "2026-08-10T14:31:00Z",
"subject": { "type": "equipment", "id": "..." },
"data": { "spn": 5246, "fmi": 0, "severity": "critical" }
}'Canonical events
Normalize once. Automate everywhere.
RideWrench accepts stable event envelopes so any ELD or telematics source can drive the same operational workflow.vehicle.location.updatedvehicle.fault.detectedvehicle.odometer.updateddriver.dvir.submittedbreakdown.reported
ELD / telematicsRideWrench event APIRules + service operations
Outbound webhooks
Keep dispatch and finance in sync.
Subscribe to the outcomes your system needs. Deliveries use HMAC-SHA256 overtimestamp.raw_body, exponential retry, and visible delivery history.breakdown.reportedandbreakdown.updatedwork_order.created,updated, andcompletedmaintenance.createdandupdated