Reference · built on requestConnectorFleet & telematics

Webfleet

Vehicle positions, trips, events, driver data, and orders from Webfleet through the WEBFLEET.connect CSV, JSON, and SOAP API.

Request accessPricing ↗

About

Webfleet is the fleet management service from Bridgestone Mobility Solutions, fed by LINK tracking units and driver terminals. WEBFLEET.connect is its integration API: one endpoint at https://csv.webfleet.com/extern, an action parameter per function, CSV by default or JSON with outputformat=json, and SOAP services with WSDLs at soap.webfleet.com. Message queues deliver tracking and order messages that you pop and acknowledge.

Through Fibric, an operator replicates trips and events, reads remaining driving times, and proposes an order, a text message, or an area. You approve it. The action is sent once and a receipt records what was sent and how to withdraw it.

This is a reference listing. It documents what Fibric would read from Webfleet and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Objects and last positions through showObjectReportExtern, and vehicle properties through showVehicleReportExtern
  • Trips through showTripReportExtern, replicated continuously by the highest tripid seen, or on demand by date range
  • Event notifications through showEventReportExtern, plus showSpeedingEvents, showAccelerationEvents, and showIdleExceptions
  • Drivers through showDriverReportExtern, the OptiDrive indicator, and getRemainingDrivingTimesEU under EU rules
  • Diagnostic trouble codes through getObjectDTCs and getDiagnosticFaults, with classification and recommended actions
  • Tracking and order messages through message queues: createQueueExtern, popQueueMessagesExtern, then ackQueueMessagesExtern
  • Maintenance schedules and tasks through showMaintenanceSchedules and showMaintenanceTasks

Proposed actions

  • Target capability: propose an order to a vehicle through sendOrderExtern or sendDestinationOrderExtern, with updateOrderExtern and cancelOrderExtern for changes
  • Target capability: propose a text message to a driver terminal through sendTextMessageExtern
  • Target capability: propose acknowledging or resolving an event through acknowledgeEventExtern and resolveEventExtern
  • Target capability: propose resolving a maintenance task through resolveMaintenanceTask
  • Target capability: propose an area through insertArea, with its assignments and schedules

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Send the next job to the terminal

    The operator drafts an order with destination, text, and time tolerance. On approval it goes out through sendDestinationOrderExtern and every driver action on it returns as an order message.

    With Field Dispatch

  • Plan around remaining driving time

    getRemainingDrivingTimesEU returns each driver's remaining times under EU rules. The operator checks planned orders against them and proposes a reassignment where the day will not fit.

    With Driver Hours

  • Route a trouble code to the workshop

    getObjectDTCs returns fault codes with classification and recommended actions. The operator groups them per vehicle and proposes a maintenance task for approval.

    With Vehicle Fault

  • Reduce idling by site

    showIdleExceptions lists idling beyond the configured threshold. The operator totals it by object and address and proposes which cases a manager should raise.

    With Idle Watch

Requirements

  • A Webfleet account and an API key requested through the Webfleet support form, under Integration and API key request
  • A Webfleet user with WEBFLEET.connect selected under Interfaces and system rights set for Orders, Areas, and Reports
  • WGS84 coordinates for any action that inserts addresses or sends orders
  • A queue created with createQueueExtern for each message class you want to receive, popped and acknowledged in sequence
Authentication
HTTP Basic Auth with a Webfleet username and password, the account name as a request parameter, and a 36-character apikey issued by Webfleet; SOAP calls pass accountName, userName, password, and apiKey instead.

Limits

  • Each action has its own request limit: showObjectReportExtern 6 per minute, showTripReportExtern 1 per minute, popQueueMessagesExtern 10 per minute, createQueueExtern 10 per 24 hours
  • popQueueMessagesExtern returns at most 500 messages per call; queue messages expire after a default TTL of 14 days
  • Trip replication should run no more than once every 15 minutes and returns at most 10000 entries per call
  • One position per minute is standard through WEBFLEET.connect; more needs the HD Tracking additional service

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Webfleet ↗

Questions and answers

Is WEBFLEET.connect REST?
No. It is one HTTPS endpoint, https://csv.webfleet.com/extern, that takes an action parameter such as showObjectReportExtern and returns CSV, or JSON when outputformat=json is set. Some order actions accept POST bodies. The same functions are also exposed as SOAP services with WSDLs at soap.webfleet.com.
How do request limits work?
Every action lists its own limit in the reference, for example 6 requests per minute for showObjectReportExtern and 300 per 30 minutes for sendOrderExtern. For continuous tracking data Webfleet points you to message queues instead of repeated report calls.
How do I get an API key and a user?
Customers request a key through the Webfleet support form, choosing Integration as the product and API key request as the category. Then create a user in Webfleet, select WEBFLEET.connect under Interfaces, and set its rights for Orders, Areas, and Reports.
Ask about Webfleet

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Webfleet through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy