RideWrench developer platform

Build service operations into any app or workflow.

Use RideWrench headlessly for provider operations, fleet service management, dispatch, estimates, invoices, payments, telematics events, and workflow automation.
Choose an SDK Download OpenAPI
Use supported SDKsTyped JavaScript and dependency-free Python clients.
Embed operationsProvider and fleet resources through stable versioned APIs.
Automate outcomesSigned lifecycle events with durable retry and delivery IDs.
Organization-owned access

Fleet and provider keys have separate authority and can be revoked independently.

Least privilege by default

Scopes and provider location limits constrain every connected system.

Safe workflow writes

Idempotency keys make repeatable operations predictable without duplicate work.

Headless toolkit

Start with your stack.

Every artifact targets the same production API contract and supports both organization types.
JavaScript + TypeScript

Node.js, serverless, edge, and modern browser runtimes with full type declarations.

import { RideWrench } from "@ridewrench/sdk"
Python

A dependency-free Python 3.8+ client for backend services, automation, and data workflows.

from ridewrench_sdk import RideWrench
OpenAPI + Postman

Generate clients, validate contracts, explore calls, or import requests into your existing API toolchain.

OpenAPI 3.1 · REST JSON · Bearer auth

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/fleet Fleet identity and authority
  • GET · POST · PATCH /api/v1/equipment Mixed fleet assets and telematics state
  • GET · POST · PATCH /api/v1/breakdowns Roadside events
  • GET · POST · PATCH /api/v1/maintenance Planned work
  • GET · PATCH /api/v1/work-orders Provider service lifecycle
  • GET /api/v1/dvir Inspection 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.updated
  • vehicle.fault.detected
  • vehicle.odometer.updated
  • driver.dvir.submitted
  • breakdown.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 over timestamp.raw_body, exponential retry, and visible delivery history.
  • breakdown.reported and breakdown.updated
  • work_order.created, updated, and completed
  • maintenance.created and updated

Provider integrations

Keep your shop, dispatch, and customers in sync.

Active service providers can connect their existing systems with provider-owned API keys, OAuth, location permissions, and signed webhook subscriptions.
  • Manage customers, assets, appointments, direct work orders, service catalogs, and branch inventory.
  • Receive and accept fleet work orders; assign technicians and share arrival estimates.
  • Submit estimates and invoices, then reconcile internal or external settlements.
  • Install apps across provider organizations with consent and PKCE.
  • Embed appointment scheduling and replay versioned production or sandbox webhooks.
Open provider console