Connect your AV platforms
ApexAV reads your rooms and devices from the platforms you already run, so the fleet keeps itself current instead of somebody maintaining a spreadsheet. Each connection needs credentials that only an administrator of that platform can create, and in one case a paid add-on that is easy to miss.
This page tells you what to have ready before you start. Nothing here needs ApexAV open — this is homework in your own vendor consoles.
Before you start
- You need to be an owner or admin in ApexAV to add a connector.
- Each platform below needs its own administrator. That may not be you: the person who can create a Cisco integration is often not the person who runs AV.
- Gather credentials into something you can paste from. You will not be able to read most of them a second time.
What connects today
| Platform | You get | Who has to help |
|---|---|---|
| Cisco Control Hub | Rooms, devices, status, firmware | A Control Hub full administrator |
| Logitech Sync | Rooms, devices, and room utilisation | A Sync organisation administrator |
Everything else on the roadmap is listed at the end.
Cisco Control Hub
ApexAV talks to Control Hub as a Service App — an integration that belongs to your organisation rather than to one person's login. This matters: an integration tied to an individual stops working the day that person leaves.
What to create, in Control Hub:
- A Service App, under Apps → Service Apps.
- Authorise it for your organisation. A Service App is created by a developer but must then be approved by a full administrator before it can read anything. This is the step people miss.
What to bring back:
- Client ID
- Client secret
- Refresh token
The refresh token is the one that matters day to day. ApexAV exchanges it for a short-lived access token roughly every fortnight, without anyone signing in. If the refresh token is revoked, the connection stops and the rooms go stale.
Keep the token somewhere you can find it
Control Hub shows the secret and refresh token once, at creation. If you lose them the fix is to generate new ones, not to look them up.
Logitech Sync
Sync authenticates differently: instead of a token, it uses a certificate and private key pair that identifies your organisation, presented on every call.
What to create, in Sync:
- A certificate and key pair for API access.
- Note your organisation ID.
What to bring back:
- The certificate file (PEM)
- The private key file (PEM)
- Your organisation ID
Sync Insights has to be enabled on your account
This is the failure that looks like a broken integration and is not one. Without the Insights add-on, Sync accepts your certificate, recognises your organisation, and then refuses the data with ADDON_NOT_ENABLED. Everything about the connection is correct; the entitlement simply is not on the account.
If ApexAV reports that error, the fix is with your Logitech account team, not with your credentials.
Room utilisation — how much each room actually gets used — comes from Insights. Without it you can still get rooms and devices, but not the usage figures.
What happens after you connect
- ApexAV pulls your rooms and devices and matches them against anything it already knows about, so connecting a second platform enriches your existing rooms rather than duplicating them.
- The sync repeats on a schedule. You do not need to re-enter anything.
- Rooms appear under Sites & Rooms, devices under Infrastructure.
If a sync fails, the connector reports why rather than silently going quiet.
Not connected yet
These are on the roadmap. If you want to be ready, the prerequisites are worth knowing now, because they involve the same administrators and the same approval delays:
| Platform | What it will need |
|---|---|
| Zoom Rooms | A Server-to-Server OAuth app: account ID, client ID, client secret |
| Google Meet | A Google Workspace service account with domain-wide delegation, plus an administrator address for it to act as |
| Mersive Solstice | A small agent installed on your network. Solstice has no cloud API, so the data has to be collected locally |
| Microsoft Teams Rooms, Crestron, Q-SYS, Biamp | Not yet specified |