Public documentation

Connect cameras to FireMonitor without guesswork. From frame to alert.

Straightforward guides for sending images, authenticating servers, testing the webhook and understanding how AI turns existing cameras into operational monitoring.

cameraWebhook

curl -X POST https://api.firemonitor.com.br/api/recognization/frame \
  -H "Authorization: Bearer fm_int_..." \
  -F "cameraId=torre-norte" \
  -F "image=@frame.jpg"

{ "hasSmoke": true, "severity": "high", "alertId": "..." }

1. Register the camera

Create the camera in the app, then set position, bearing and monitored region.

2. Send frames

Use local RTSP, your own worker or POST to the webhook with image and cameraId.

3. Receive alerts

AI validates smoke, creates an alert, plots the map point and notifies the team.

Pipeline

How integration works

FireMonitor receives camera images, normalizes metadata, runs visual analysis, stores evidence and publishes alerts to the dashboard, map and notifications.

Frame webhook

HTTP endpoint for servers, DVRs, scripts and local bridges to send images with cameraId, optional coordinates and Bearer token.

Authentication

Use integration tokens for 24/7 production. Firebase ID tokens are best for quick browser tests.

Field operations

Cameras, regions, calibration, wind, triangulation and reports stay in the app so the team can review events without chasing context.

API

Basic webhook contract

The public interface is intentionally small: camera, image and authentication. Operational details stay in the camera record.

Main fields

`cameraId`	string	required
`image`	file	multipart
`imageUrl`	string	optional
`bearing / fov`	number	optional
`lat / lng`	number	optional

Short response

{
  "ok": true,
  "hasSmoke": true,
  "confidence": 0.85,
  "severity": "high",
  "alertId": "-NyX123",
  "triangulated": { "lat": -21.13, "lng": -50.38 }
}

RTSP cameras on a local network

Run a bridge on a farm computer to capture frames and forward them to FireMonitor.

Cameras with image URLs

Send an HTTPS imageUrl or signed URL when the frame already lives in storage.

Controlled test

Use signed-in docs to generate a token, attach a real frame and inspect the webhook response.

Want to validate with a real camera?

Create an account, generate a token in the internal docs and send the first test frame in a few minutes.

Contact team