Authenticate against the Verizon Connect Reveal REST API using Base64-encoded integration credentials to pull fleet vehicle location data
domain: reveal-help.verizonconnect.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Submit an integration request; Verizon Connect emails integration user credentials plus a link to the Developer Portal
Register on the Developer Portal separately from the Reveal REST integration credentials — the two credential sets are not interchangeable
Note the assigned app ID, required to authenticate API requests
Base64-encode the Reveal REST integration username/password (not the developer portal login) in each API request
Test calls against the sandbox account before pointing at a production Reveal account
Known gotchas
There are two distinct credential sets — Developer Portal login credentials and Reveal REST integration credentials — and API calls specifically require the latter, Base64-encoded, not the portal login
Credentials are only viewable in the original issuance email from Verizon; losing that email means requesting a reissue rather than retrieving them from the portal
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?