Build on TRIKDIS
hardware.

Receive events, control and configure alarm panels and communicators, and manage your fleet — through one documented REST API. For monitoring platforms, access control and building management, PSIM/VMS and partner portals.

One documented REST API — JSON over HTTPS
0
Capability areas: events, control, fleet
0
Formats & protocols spoken
0
One REST API to receive events, control panels, and manage your fleet. Built on the TRIKDIS hardware your customers already trust — not another box.
Made for integrators

If you build software that needs to see or drive alarm hardware, the IPcom API is your integration surface.

Monitoring & CMS

ARC / central-station software makers receiving events in the formats you already process.

Access & building mgmt

Access control and building-management platforms driving doors, gates and outputs.

PSIM / VMS

Physical security and video platforms adding TRIKDIS panels as a data and control source.

Partner portals

Partners with their own portals exposing TRIKDIS devices to their end customers.

Three things, one API

Receive, control, manage — everything over REST/JSON, where supported by the panel or communicator.

Receive events

Real-time panel events (alarms, arm/disarm, zones, faults and restores) and system events (connectivity, cellular and receiver status), with history and logs — delivered through JSON, webhooks, TCP or supported monitoring formats.

Control & configure

Arm, disarm, set stay/sleep, bypass zones, silence sirens, trigger panic/fire/medical and drive outputs/PGM for gates and relays. Read and update settings, panel users and schedules on TRIKDIS panels and communicators.

Manage the fleet

Query live device status, schedule reboots, run firmware updates and monitor IPcom server health — keep an entire estate of communicators current and observable.

Speaks what your platform already uses

Deliver events over modern web transports or the monitoring formats your ARC has run for years — no bespoke receiver software on your side.

Access you control, per partner

Every integration authenticates over HTTPS and sees only what its scope allows.

JWT over HTTPS

Token-based authentication on every request, encrypted end to end.

Scope-based permissions

Grant capabilities per integration — read events, control panels or manage fleet, independently.

Per-user device visibility

Each partner sees only the devices assigned to them — no cross-tenant exposure.

Configurable token lifetimes

Set how long credentials stay valid to match your security policy.

Three steps to your first call

Public overview first, partner access when you’re ready, then build against the REST/JSON API.

01
Review the overview & PDF

Read the public capabilities page — every endpoint area, format and security control, no login required.

02
Request partner access

Submit the access request. Once approved you receive credentials and the full API documentation.

03
Build against REST/JSON

Point your platform at IPcom, authenticate with your JWT, and start receiving events and sending commands.

Ready to build on TRIKDIS?

Request API access and our team reviews your integration. Approved partners get full documentation and credentials.

What are you looking for?
Press Enter or "Search". Close — Esc.

CONSULT OUR TEAM

Fill out the form below, and we will be in touch shortly.

Choose language

Choose language

Elija idioma

Pasirinkite kalbą