Xeqmate integrations cover both directions of the operation: inbound, cameras, DVRs and NVRs of any brand over RTSP, RTMP or P2P; outbound, alerts delivered to your system over webhook, to your team over Telegram and push, data you can query through the external API, and integrations with public-safety programmes.
Xeqmate integrates on three fronts: video in (IP cameras, DVRs and NVRs of any brand over RTSP, RTMP or P2P, with no hardware swap), events out (webhooks with signed JSON, Telegram alerts and push notifications) and data queries through the external REST API. On top of that, it connects to the Brazilian public-safety programmes Smart Sampa, Muralha Paulista, Alerta Brasil and Helios MG.
Each front is detailed below. If your question is about the platform itself — recording, AI, multi-tenancy — start on the VMS SaaS page.
What separates them is who opens the connection — and that is what decides which one works on your network.
In RTSP, the Xeqmate server connects to the camera, DVR or NVR and requests the stream — it is the common language of CCTV, present in virtually every professional IP camera. Because the platform opens the connection, the device has to be reachable over the internet (static IP, DDNS with a forwarded port, or a VPN). It is the two-way route, and it also carries PTZ commands.
In RTMP the direction flips: the camera or encoder pushes the video to a dedicated URL the platform generates. The connection is outbound, so it needs no public IP, no DDNS and no open port — it works behind CGNAT, on residential fibre, on 4G and at sites where nobody has router access. It requires a device with RTMP push in its firmware.
P2P cameras keep a closed tunnel to their own manufacturer cloud. For some supported manufacturers, Xeqmate registers the camera over P2P (serial number, RTSP port and credentials) and pulls the video through that tunnel — without a public IP, as in RTMP. For every other model, the route is to enable the camera own RTSP or RTMP.
And ONVIF? ONVIF is a standard for discovering and controlling cameras — it lists the streams and reports each URL, but it does not carry video by itself: underneath, the video travels over RTSP. In practice, ONVIF cameras join Xeqmate over RTSP. The three protocols are broken down, with the network scenario for each, in the article RTSP, RTMP and P2P: what is the difference.
The events handled in the event center also leave the platform — to your system, to Telegram and to the team phones.
On every plate alert, vehicle-attribute alert or face alert, the platform makes an HTTP POST to your system URL with a fixed, documented JSON shape. Delivery carries a token in the Authorization: Bearer header and an HMAC signature in X-Xeqmate-Signature, so your system can validate the origin. You choose which cameras and event types trigger the send, and each camera and event can carry an external code — the identifier your system already uses.
Each user can get alerts straight in their own Telegram by setting a Chat ID in their profile and choosing, in the preferences, which notification types come through there. Alerts can also go to Telegram groups — handy for a monitoring team following everything in one channel.
Alerts arrive as push notifications and popups in the web dashboard and in the Android and iOS apps, with per-user alert preferences — everyone gets only what matters to their role.
The webhook pushes events to your system; the external API is the other direction — your system queries Xeqmate. It is a REST API with a per-account token (enabled by a platform administrator), HTTPS only, covering cameras, recording clips with signed video URLs, plate and face reads and user management, with pagination, a published rate limit and every call audited.
The endpoints, example requests and response codes are documented on the Xeqmate API page.
Only the cameras you pick join each programme; the agency receives only the data type the programme covers, and the rest of the operation stays private. The four programmes below are the Brazilian networks Xeqmate connects to natively; elsewhere, the same webhook and API mechanism does the job. Details on public safety solutions.
Automatic delivery of plate reads to Helios, the integrated video surveillance platform of the Minas Gerais public security service (Brazil), feeding the state vehicle monitoring database.
Two-way sharing with the City of São Paulo platform: cameras, plate reading and facial recognition integrated into the municipal video surveillance network.
Integration with the São Paulo State Government electronic perimeter: sending faces and plates and alerts of interest, with the cameras registered in the state database along with their location and capabilities.
Querying and sending plates to Alerta Brasil, the Brazilian Federal Highway Police national database, cross-referencing your LPR camera reads against vehicles of interest across the country.
Joining follows the same path in every programme: accreditation with the agency, registering the integration in the platform, and selecting the participating cameras one by one. With Alerta Brasil there is no credential to request — the integration uses the platform own credential with the Federal Highway Police.
Yes, through two complementary routes: the webhook, where Xeqmate sends plate and face alerts to your system URL in a fixed, signed JSON shape; and the external API, where your system queries cameras, recordings, reads and users. Your system only needs to accept HTTP calls.
Not necessarily. With RTMP, the camera pushes video to the platform over an outbound connection — it works behind CGNAT, on 4G and with no router access. The same holds for P2P on supported manufacturers. RTSP is the route that requires a reachable address (static IP, DDNS with a forwarded port, or a VPN).
ONVIF cameras join the platform over RTSP. ONVIF is a discovery and control standard — it reports the stream URL, but the video itself travels over RTSP. If a camera "has ONVIF", it has RTSP, and that is how it is registered.
Plate alerts, vehicle-attribute alerts and face alerts from the cameras you link to the integration. Each delivery is a POST with a fixed JSON shape, a Bearer token and an HMAC signature in the X-Xeqmate-Signature header, with a unique delivery id so you can discard duplicates.
Each programme has its own accreditation process with the agency (a membership agreement or a partnership). Once you have the credentials, the integration is registered in the platform and you select, camera by camera, what takes part. With Alerta Brasil the credential belongs to the platform — there is no key to request.
No. Only the cameras you select join the integration, and the agency receives only the data type the programme covers — live video, plate reads or the camera registry, as the case may be. Recordings, reports and the rest of the operation stay private.
30 minutes with our team: we connect one of your cameras live and walk through webhooks, the API and the integrations along the path that makes sense for your system.
We reply within one business day · no credit card, no install, no commitment