Reference · built on requestConnectorFleet & telematics

Verizon Connect Reveal

Vehicle locations, GPS plots, and fleet alerts from Verizon Connect Reveal, with work orders created through Reveal Integration Services.

Request accessPricing ↗

About

Verizon Connect Reveal is the fleet tracking product behind Verizon's telematics units. Its REST interface, reached through the Verizon Connect Integration Manager, exposes vehicles, drivers, users, groups, geofences, and work orders, and can push GPS plots and alert messages to an HTTPS endpoint you host. Objects are addressed by identifiers you set in Reveal: Vehicle Number, Driver Number, Place ID, and Work Order Number.

Through Fibric, an operator reads a vehicle's last location, receives alert webhooks, and proposes a work order or a vehicle record change. A dispatcher approves it. The write happens once, with a receipt of what changed and how to undo it.

This is a reference listing. It documents what Fibric would read from Verizon Connect Reveal 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

  • Vehicle location through GET /rad/v1/vehicles/{vehicleNumber}/location, keyed by the Vehicle Number set in Reveal
  • GPS plots pushed in near real time by the GPS Webhook as each new plot arrives from the tracking unit
  • Alert Webhook messages for Ignition, Harsh Driving, Excessive Idle, Speeding, Long Stop, Geofence, Diagnostic Trouble Codes, HOS Violation, Unassigned Miles, Panic, and Towing
  • Vehicles, Drivers, Users, Groups, and Geofences as Reveal objects, each carrying its unique identifier
  • Work Orders with their Work Order Status Codes and Work Order Type Codes, which exist only through the API

Proposed actions

  • Target capability: propose a work order through POST /pas/v1/workorders with WorkOrderNumber, DriverNumber, Address, ScheduledDateUtc, and status and type codes
  • Target capability: propose a vehicle record update through PUT /cmd/v1/vehicles/{vehicleNumber}, covering RegistrationNumber, VIN, Make, Model, Year, and TankCapacity

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

What you can build

  • Create a work order from an approved job

    The operator drafts a work order with driver, address, and scheduled time. On approval it is posted to /pas/v1/workorders and appears against the driver in Reveal.

    With Field Dispatch

  • Tell the customer when the van is close

    Vehicle location and GPS Webhook plots give position and heading. The operator computes an arrival window and proposes the notice text before anything is sent.

    With ETA Notice

  • Turn Excessive Idle alerts into a weekly list

    Excessive Idle alert messages carry vehicle, driver, place, and time. The operator totals them and proposes which sites and drivers to raise with a supervisor.

    With Idle Watch

  • Explain unassigned miles

    Unassigned Miles and Unassigned Vehicles alerts show driving with no driver logged. The operator proposes the likely driver from schedule data for a manager to confirm.

    With Unassigned Driving

Requirements

  • A Reveal account plus Reveal REST Integration credentials issued by your Customer Care representative
  • An app registered in the Verizon Integration Manager, which provides the app ID used in every request
  • Vehicle Numbers, Driver Numbers, and Place IDs populated in Reveal, since the APIs address objects by these identifiers
  • For webhooks, an HTTPS endpoint on port 443 with TLS 1.2 or later, Basic authentication, and no certificate warnings
Authentication
Two credential sets: Verizon Integration Manager credentials that register an app and yield an app ID, and Reveal REST Integration credentials exchanged at https://fim.api.us.fleetmatics.com/token for a Bearer token sent as Authorization: Atmosphere atmosphere_app_id=<app id>, Bearer <token>.

Limits

  • A token is valid for 20 minutes and must be refreshed from the token endpoint
  • The vehicle location call should not run more often than every 3 to 5 minutes per vehicle
  • Alert Webhook deliveries are retried every 10 seconds for 5 minutes, then the message is discarded
  • The Test Client runs against the customer's real Reveal account; changes made through it are applied there

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 Verizon Connect Reveal ↗

Questions and answers

What credentials does Reveal Integration Services need?
Both of these: Verizon Integration Manager credentials, created at the developer portal, to register an app and get its app ID; and Reveal REST Integration credentials from Customer Care, Base64-encoded as username:password and sent as Basic auth to the token endpoint. Without both you cannot make a request.
How do alert webhooks get switched on?
The Alert Webhook Service feature must be enabled on the account. An administrator then selects the option to use the Reveal Alert Webhook API in the Alert Recipients step of an alert policy. Alerts arrive as JSON with common fields plus alert-specific ones such as Geofence Name.
Which region hosts the API?
US accounts use https://fim.api.us.fleetmatics.com and EU accounts use https://fim.eu.fleetmatics.com for the token endpoint. Use the host that matches the region of your Reveal account.
Ask about Verizon Connect Reveal

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 Verizon Connect Reveal 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