Dashcam Wi-Fi API

Overview now — reference and guides coming soon

This page introduces the Dashcam Wi-Fi API and how it relates to the cloud Fleeta Open API. The endpoint reference (schemas, examples, result codes) and the per-topic guides are being finalized and will be published in this section. Follow the changelog for the release.

The Dashcam Wi-Fi API is served by the dashcam itself. A phone, laptop or field tool joins the dashcam's Wi-Fi access point and talks to it directly — no internet, no Fleeta account, no API key. It is the protocol the official BlackVue / Fleeta apps use when they are next to the vehicle, and it is the only channel for Wi-Fi-only dashcams (the ones the cloud API lists with category: wifi and answers with 422 cloud_only for cloud-only features).

Two ways in. The cloud path (left) is fleet-wide and needs a subscription and an LTE-connected dashcam; the local path (right) works for every dashcam, needs nothing but the access-point password, and reaches one vehicle at a time.

Dashcam address     10.99.77.1  (fixed — clients get 10.99.77.2 – .254)
HTTP                port 80, HTTP/1.1, JSON, "Connection: close" per request
Live view           rtsp://10.99.77.1:8554/livePlay?channel=front|rear|option   (H.264)
Authentication      none — joining the access point is the only gate
Concurrency         one client at a time (GET /accessible heartbeat, every 3 s)
Protocol version    1.40 (2026-05-28)

Who this is for

You are	You use it to
A firmware partner building a dashcam that must work with the BlackVue / Fleeta apps	Implement the device side — fixed IP and ports, HTTP Range on recordings, the single-client lock, sibling-file deletes. An implementer checklist ships with the reference.
An app or field-tool developer	Pull footage from a vehicle without the cloud, apply settings in bulk, configure the SIM / APN on site, pair an SOS button, sync the clock
An offline or mixed fleet	Reach Wi-Fi-only dashcams that the cloud API cannot (422 cloud_only), or vehicles without LTE coverage
QA / production test	Script an end-of-line check: deviceInfo → cameraStatus → vodList → settings

What you can do

Ask	Operations
Connect and hold the session	GET /accessible · GET /deviceInfo · GET /cameraStatus
Recordings on the SD card	GET /vodList · POST /vodMetadata · GET /{file}?stream= (Range) · DELETE /vodDelete
Live view	RTSP livePlay?channel=
Read and write settings	GET /settings · PUT /settings
Device and network	GET /apList · POST /setTime · GET/PUT /simInfo
Reboot, format, SOS button	POST /deviceRebooting · GET /sdFormat · GET/POST /sosButton

Each row gets its own guide with curl lines, and the endpoint reference will carry request / response schemas and every result code. There will be no Try it panel for this API — the dashcam is on a private link your browser cannot reach from this site; the curl lines are meant for a laptop that has joined the access point.

How it relates to the cloud API

	Fleeta Open API	Dashcam Wi-Fi API
Reaches	every vehicle in the fleet, from anywhere	one dashcam, from next to it
Needs	Fleeta subscription, API key, LTE-connected dashcam	the access-point password
Dashcams	category: cloud only	all — including category: wifi
Style	uniform JSON, RFC 9457 errors, plan limits	device-native JSON, per-endpoint envelopes, no limits
Writes	settings read-only, reboot, SD recall/delete behind scopes	settings writable, format, SIM, time — unauthenticated

Use the cloud API for anything fleet-wide or automated. Use the Wi-Fi API when you are physically at the vehicle, when the vehicle has no LTE, or when the dashcam is a Wi-Fi-only model. The psn you see in GET /deviceInfo is the same identifier the cloud API uses.

Security model — read before you build

• No authentication. Every endpoint is open to anyone on the dashcam's Wi-Fi link. The access-point password is the credential — keep it private, change it after a vehicle changes hands, and never bake it into an app that ships to third parties.
• One client at a time. The heartbeat locks the device to your session; another app (including the official one) is refused until you leave.
• Destructive calls have no confirmation step. GET /sdFormat erases the card, PUT /settings applies immediately, POST /deviceRebooting drops the link. Put the confirmation in your UI.
• Some fields are for the official apps only. deviceInfo.pwd is opaque; the SIM endpoint's PIN / PUK / APN password fields will be left out of the reference — do not display or store them.
• Firmware upload is not documented. The endpoint the official apps use to push firmware is partner-only; there is no public way to flash a dashcam over Wi-Fi.

What is coming

The rest of this section is being finalized against protocol v1.40 and will appear here:

• Connect — join, heartbeat, identity, camera channels
• Recordings — list, metadata, play / download, delete
• Live view — RTSP
• Settings — read / write the snapshot
• Device & network — Wi-Fi scan, clock, SIM / APN
• Maintenance & safety — reboot, SD format, SOS button
• Endpoint reference — every operation with schemas, examples and result codes
• Implementer checklist — the hard requirements for firmware partners

Until then, the cloud Fleeta Open API covers every cloud-connected dashcam, and AI Assistants (MCP) can query the same fleet in plain language.