Single-source integrator for control rooms, command centres & security operations — everything from one source
control∞rooms endless possibilities Request a consultation →

Barco CTRL API: Automating the Control Room and Integrating Third-Party Systems

Barco CTRL API: Configure, Operate and Maintain interfaces for control roomsAI-generated

Barco CTRL can be operated not only through its own user interface but also from other systems. For this, the platform comes with built-in programming interfaces: the Barco CTRL APIs. With them, a button panel switches a layout onto the video wall, a video management system brings the right camera to the operator workstation, and IT creates a hundred new sources without clicking through them one by one.

This article explains what the interfaces can do, how Barco has split them and what matters when integrating them into a control room. It is based on Barco’s product information, the quick start guide for the APIs and the reference documentation of the Configure API (version 1.3.0) and the Maintain API (version 1.3.1).

What the Barco CTRL API is

Barco CTRL is a software-defined platform that brings sources, operator workstations and video walls together over the IT network. The APIs make this platform accessible from outside: configuration and operation can be triggered programmatically from external systems and devices. Barco explicitly addresses operators who want to connect Barco CTRL with third-party solutions or existing applications.

Technically, the interfaces follow established standards:

  • REST over HTTPS – every request is encrypted
  • JSON as the format for requests and responses
  • OIDC (OAuth 2.0) with JWT access tokens for authentication and authorisation
  • OpenAPI specification for each API, plus interactive documentation directly on the Barco CTRL server
  • Access via port 443 to an on-premises Barco CTRL installation

For an integrator, this means no proprietary protocol and no special library. Any environment that can send HTTPS requests can talk to Barco CTRL.

Three APIs for three jobs

Barco has deliberately split the interface into three separate APIs. According to the manufacturer, this helps build applications along security best practices and follow the principle of least privilege: an application only gets the API it needs for its job.

API What it does Typical use
Configure API reads and changes the configuration: create, read, replace and delete sources (camera, Barco encoder, RDP, VNC), retrieve camera templates automating recurring administrative tasks, such as creating cameras in bulk; an external reference keeps each source linked to the third-party system
Operate API reads the inventory (e.g. sources and workplaces) and controls which content is shown on the individual workplaces custom operator workflows, connecting other equipment in the control room
Maintain API reads system status, devices with firmware and network data, certificates, users, roles, groups, API clients, LDAP integration and audit and log server settings compliance and security evidence, for example for NERC CIP; some endpoints require the “Compliance Reporting” licence
According to Barco product information and reference documentation. According to the documentation, the Configure API does not yet support web sources.

Each of the three APIs has its own guide, plus an overall quick start guide. Barco lists the documents in its support area for the CTRL software and the SAS-050, SAN-050 and SAS-500 devices.

How access is set up

The APIs work without a user login. Instead, the administrator creates a dedicated API client in the Barco CTRL system interface and assigns it a role. The application then authenticates via the client credentials flow with a client ID and client secret – the standard method for machine-to-machine connections.

  • “Admin” role for applications that read or change the system configuration
  • “Operator” role for applications that control which content appears on the screens
  • The access token is valid for ten minutes; after that, the application retrieves a new one with the same credentials
  • Every request carries the token in the Authorization header; without a valid token the server responds with “401 Unauthorized”

What the API makes possible in the control room

Barco itself names three fields of application:

  • Screen content by task: the content at the workstation changes automatically to match the task the operator is currently working on.
  • Integration with a video management system (VMS): camera images and video workflows are linked directly with Barco CTRL.
  • Compliance: depending on the industry, control room systems must meet regulatory requirements and be able to deliver compliance and security data. Barco cites NERC CIP in North America as an example.

In our projects, typical everyday tasks are added:

  • Button control for the video wall: a panel with labelled macro keys switches stored layouts and perspectives – one key press instead of a menu search in the middle of an incident.
  • Tablet operation: shift supervisors or incident commanders select video wall content without having to go to an operator workstation.
  • Creating sources in bulk: when dozens of cameras are added, the configuration is generated from a list instead of by hand.
  • Event-driven display: when a third-party system reports an event, the associated source appears at the right workstation.

A note on tablet operation: Barco explicitly points out that pure browser applications cannot store the credentials securely. A tablet or web interface therefore never talks to Barco CTRL directly, but through its own backend that keeps the credentials safe.

Which of these workflows can be implemented with which API is clarified in the project based on the current Barco documentation – the interfaces grow with every version.

Security: why the split matters

An interface that can control a control room is also an attack path. That is why the split into three APIs is more than tidiness. A button panel that only switches layouts does not need access to the configuration. A compliance tool that pulls reports does not need to control anything. Giving each application only the matching API and the necessary rights limits the damage if a connected system is compromised.

In its quick start guide, Barco sets clear rules for operation:

  • Do not develop on the production system. API calls can interfere with regular control room operation. Development and testing take place on a separate instance – a demo or training system – and the system is backed up before first use.
  • One API client per application. This way each integration can be disabled individually when troubleshooting or during maintenance.
  • Credentials belong in a vault. Client ID and secret belong in a password manager or vault, never in the program code – otherwise they will sooner or later end up in a code repository.
  • A valid certificate instead of the factory certificate. Out of the box, Barco CTRL uses a self-signed certificate. For production, a valid certificate is installed instead of disabling certificate verification.

The rights are also more finely grained than just “Admin” or “Operator”: when reading sources, an application sees either all sources or only those it is permitted to see, according to the reference documentation. Passwords for RDP, VNC or camera sources are encrypted with a public key of the system before transmission.

Authentication via OIDC with JWT access tokens fits the requirements that NIS2 and the Cyber Resilience Act bring to control rooms: traceable identities, time-limited permissions and encrypted connections. The Maintain API also delivers the data an operator needs for evidence and audits: users with last login and lockout status, API clients with the time of the last secret rotation, certificate expiry dates, password policy and protection against password guessing attacks, the connection to audit and log servers (syslog/SIEM) and the firmware and network data of every device. Some of these queries – such as password policy, audit settings or open device ports – require the “Compliance Reporting” licence.

Stable integrations through versioning

A control room runs for many years, and software is updated several times during that period. Barco has therefore defined a dedicated lifecycle for the APIs based on semantic versioning; the major version is part of every request path (such as /api/configure/v1/), and a dedicated endpoint returns the exact version. This lets integrators see which versions may contain changes that break existing integrations. A platform update thus becomes plannable instead of silently disabling the button panel or the VMS link.

Control room solutions from a single source

controlrooms plans and integrates Barco CTRL as a single-source provider – from the video wall to KVM and operator workstations to the connection with your existing systems. For API integrations, we first clarify the workflows in operation, then define which API is needed with which rights, and test the integration before commissioning. After go-live, the integration remains part of our service so that it keeps running reliably after platform updates.

Planning an integration with Barco CTRL? Get in touch.

Sources: Barco, “Barco CTRL APIs”, barco.com, retrieved 25 September 2026; Barco CTRL APIs Quick Start Guide (R591984, v02); reference documentation Barco CTRL Configure API 1.3.0 (R591987) and Maintain API 1.3.1 (R591991).

Visit our showroom in Vienna Prater or Wieselburg

Technology for control rooms, command centers and KVM workspaces is best evaluated live. In the controlrooms showroom we demonstrate video walls, KVM, operator desks and typical 24/7 scenarios working together in real conditions.

Appointments by arrangement. controlrooms GmbH supports you with analysis, planning, integration and ongoing service.

Request a showroom appointment

This content comes from an external provider (YouTube, Vimeo or Google Maps) and only loads once you accept marketing cookies.
FAQ

Frequently asked questions about the Barco CTRL API

What is the Barco CTRL API?

A set of built-in programming interfaces that let you configure and operate Barco CTRL from external systems and devices. It follows the REST paradigm over HTTPS with JSON and is documented via OpenAPI.

Which three APIs are there?

The Configure API reads and changes the configuration, such as sources. The Operate API controls which content appears on the workplaces. The Maintain API reads status and configuration, for example for compliance and security evidence.

How does an application authenticate with the API?

The administrator creates a dedicated API client with the Admin or Operator role in Barco CTRL. The application uses the client ID and client secret to obtain an access token that is valid for ten minutes and sends it with every request.

Does the API require a separate licence?

Barco’s product information, the quick start guide and the Configure and Maintain API reference name only one licence: “Compliance Reporting”. It is required for individual Maintain API queries such as password policy, audit settings or open device ports. Which licences a specific project needs is clarified based on the Barco quotation.

Can I control Barco CTRL with a button panel or a tablet?

Yes, external control devices can be connected through the interfaces. Button panels switch stored layouts, tablets let shift or incident supervisors select content. A tablet or web interface needs its own backend, because the browser cannot store the credentials securely.

Can the API disrupt ongoing operation?

Yes, Barco itself points this out. Integrations are therefore developed on a separate test or demo instance, the production system is backed up beforehand, and each application gets its own API client that can be disabled individually.

Do integrations keep working after an update?

Barco manages the APIs with semantic versioning. This shows which versions may contain changes that affect existing integrations, so updates can be tested in a targeted way.

Share
← Home More posts

Let's talk about your control∞room.

Whether new build, modernisation or expansion – we bring the experience of more than 25 years. No obligation, personal, on equal terms.

Request a consultation →
Request a consultation →