Integration Guide

Connect your TMS or ELD
in minutes.

ValveRide Flow connects to any dispatch system via webhook or API. Full technical documentation, credentials, and integration support are provided to customers after onboarding.

Get API access →See integrations →

How integration works

Three steps to live fuel plans.

01

Get your credentials

After onboarding, you receive a tenant slug, webhook secret, and API key scoped to your fleet. All credentials are rotatable at any time from your portal.

02

Configure your dispatch system

Add the Flow webhook URL as an outbound destination in your TMS or ELD. Any system that supports outbound HTTP webhooks works, with no custom software required.

03

Dispatch and receive plans

From that point, every dispatch automatically triggers a fuel plan in under 2 seconds. The plan is returned in the webhook response and available in your portal immediately.

API capabilities

Everything accessible via REST API.

The full ValveRide Flow feature set is available via API: fuel plan generation, trip management, compliance data, driver plan delivery, and export formats. Every feature your portal users can access, your systems can access programmatically.

Full API reference documentation, including endpoint specifications, authentication requirements, request schemas, and response formats, is provided to customers as part of onboarding. Enterprise customers receive dedicated integration support.

EXAMPLE DISPATCH PAYLOADPOST /api/v1/webhooks/your-tms
x-tenant-slug: acme-fleet
x-webhook-secret: your-secret
Content-Type: application/json

{
  "trip_id":       "TRIP-2026-001",
  "origin":        "Dallas, TX",
  "destination":   "Memphis, TN",
  "dispatch_time": "2026-03-17T08:00:00-06:00",
  "truck_number":  "T-101",
  "fuel_gallons":  45
}
RESPONSE, FUEL PLAN INCLUDED{
  "received":  true,
  "eventId":   "evt_abc123",
  "tripId":    "trip_xyz789",
  "fuelPlan": {
    "bestStop":   "Pilot Flying J, Texarkana",
    "netPrice":   3.779,
    "recGallons": 78.3,
    "estSavings": 9.42
  },
  "message": "Fuel plan generated and ready to push"
}

What the API covers

Built for your whole dispatch flow.

Every capability your portal users rely on is reachable programmatically.

Fuel Plan Generation

Trigger optimized fuel plans programmatically from any dispatch event.

Trip Management

Create, update, and retrieve trip records and associated fuel plans.

Compliance Data

Access driver compliance scores, transaction matches, and missed savings.

Export & Dispatch

Export fuel plans in CSV, Excel, or JSON formats. Push driver-safe plans to ELDs.

Webhook Events

Receive real-time events for plan generation, compliance updates, and more.

Model Context Protocol

Connect Flow over MCP.

Flow exposes an MCP server for assistants and agent platforms: ChatGPT, Claude, Grok custom connectors, Muse custom connectors, and any MCP client. Same engine as the portal: market snapshot plus fuel plan optimization.

Listing tools is open, so a client can discover what Flow offers. Calling a tool requires credentials, either an OAuth connection or a developer key. This is developer account auth, not a fleet tenant login, and it does not access tenant fleet records.

MCP SERVER (STREAMABLE HTTP, POST)https://app.valverideflow.com/api/mcp
AUTH OPTION 1, OAUTHDiscovery:
https://app.valverideflow.com/.well-known/oauth-authorization-server
Scopes: snapshot, optimize
AUTH OPTION 2, DEVELOPER KEYAuthorization: Bearer vrf_dev_...
(x-api-key: vrf_dev_... is also accepted)
Get a key: https://app.valverideflow.com/developers

fuel_market_snapshot

Free market snapshot tool. Still requires credentials to call.

optimize_fuel_plan

Optimized fuel plan for a trip, metered per call.

Grok

Open grok.com/connectors, choose New Connector, then Custom, and paste the MCP server URL.

ChatGPT

Use Flow Inside, available as an app in the ChatGPT plugin directory.

Claude

Flow is available as a connector in Claude. In Claude, open Settings, then Connectors, then Browse, search ValveRide Flow, and Connect. More on the Flow by MCP page.

Muse and other agents

Add a custom connector with the MCP server URL, and store an OAuth connection or a developer key in the agent's credential store.

Compatible systems

Works with your existing stack.

Any TMS via WebhookIsaacSamsaraOmnitracsMotive (KeepTruckin)GeotabCustom / In-House TMSGeneric ELD / Telematics

Don't see yours? We build custom adapters for Enterprise customers. Contact us →

Security

Built secure from the ground up.

Authenticated endpoints

All API endpoints require valid credentials. Unauthenticated requests are rejected.

Signed webhook events

Every inbound webhook is verified with a cryptographic signature before processing.

Tenant data isolation

Your fleet's data is fully isolated. No cross-tenant data access is possible at any layer.

Full audit logging

Every API action is logged with actor, timestamp, and entity for compliance and forensics.

Ready to integrate?

Full API documentation and credentials are provided after onboarding. Contact us to get started. Most fleets are live within one business day.

Get API access →See integrations →