Platform integration

HikCentral API integration with enterprise systems

We connect HikCentral Professional OpenAPI with ERP, HR, and business processes: people management, access, and events—without replacing the Hikvision platform.

HikCentral Professional concentrates video, access, and events. Value appears when that platform participates in operations: identities, permissions, visitors, and automation toward ERP, HR, or other systems.

Talk to us Explore our solutions

Context

HikCentral and enterprise systems

Why an organization connects HikCentral Professional with existing applications.

Unified identities

Avoid people directories that live only in security or only in HR.

Aligned permissions

Role or site changes should reach access control with less friction.

HR and operations

Hires, exits, and moves should feed the security platform.

Visitors

Coordinate visit information with what HikCentral needs to operate.

Useful events

Move from alarms only visible in the VMS to rules, notifications, or internal systems.

HikCentral Professional OpenAPI

Integration capabilities in HikCentral Professional

Hikvision documents HikCentral Professional OpenAPI (a RESTful API) for integrating applications with the platform. The term “Hikvision API” is broader and does not always mean HikCentral. What is available depends on version, modules, licenses, and devices.

OpenAPI (RESTful)

Interface documented by Hikvision for integrating applications with HikCentral Professional. The effective catalog is validated in the customer environment.

Hikvision API vs HikCentral OpenAPI

“Hikvision API” may refer to different manufacturer products. This page covers HikCentral API integration via HikCentral Professional OpenAPI, validated in the customer environment.

Identities and access

People and permission management when the platform and licenses allow it; ERP or HR are often the usual source of that data.

Visitors and resources

Visitor and security-resource capabilities depending on enabled modules — confirmed per project.

Events and alarms

Consuming HikCentral-published events for business rules and external destinations.

Other interfaces

Besides OpenAPI there may be SDKs or other mechanisms from the manufacturer; we do not treat them as equivalents or always required.

Otiumtek integrates on those interfaces; we are not Hikvision and do not claim full compatibility with every version or module. OpenAPI is typically enabled in the platform (third-party integration), per manufacturer documentation.

Enterprise systems

ERP HR Internal apps
Otiumtek integration

sync and routing

Security platform

HikCentral Professional

Approach

How we assess a HikCentral integration

Indicative steps before committing scope.

  1. 01

    Map HikCentral Professional

    Version, modules, OpenAPI or other enabled interfaces, and current operations.

  2. 02

    Review manufacturer requirements

    Licenses, third-party integration configuration, and deployment limits.

  3. 03

    Design the flow

    Sources and destinations: HR, ERP, internal apps, notifications.

  4. 04

    Select the approach

    Onyx (directories/permissions), Tork (events), custom development, or a combination.

  5. 05

    Implement with validation

    Tests against the real environment and operational acceptance criteria.

Otiumtek solutions

Onyx and Tork with HikCentral

How our products relate to HikCentral — different ecosystem from Dahua DSS, same product roles.

Onyx — Directory and publication into HikCentral

Onyx manages people, visitors, vehicles, and permissions, and can publish that information into HikCentral. ERP or HR are often the source of the directory; Onyx does not replace HikCentral or video control.

View Otiumtek Onyx →

Tork — HikCentral events into the business

Tork receives events published by HikCentral, applies business logic, and delivers to Telegram, webhooks/APIs, or other project integrations. It is not a universal camera controller or a VMS replacement.

View Otiumtek Tork →

If the case needs a specific bridge (for example a particular ERP), we design a custom integration after validating OpenAPI and the real deployment scope.

Events

HikCentral events → rules and external systems

Conceptual flow when HikCentral events must reach notifications or other systems.

Enterprise systems

HikCentral events
Tork

sync and routing

Security platform

Notifications Webhooks / APIs External systems

Scenarios

Indicative business scenarios

Typical evaluation cases — not a list of closed projects.

ERP / HR → people and permissions

Hires, exits, and org changes from the people system feed the directory that publishes into HikCentral (typically via Onyx), with less double entry.

Visitors and authorizations with Onyx

Visitor management and entry authorizations in Onyx, with publication into HikCentral when the environment and licenses allow—without operating video from Onyx.

Access aligned with operations

Groups and permissions that follow the organizational structure, published into HikCentral when OpenAPI and licenses allow it.

Event processing

Events published by HikCentral → business rules → notifications, webhooks/APIs, or other systems (Tork or another integration).

Internal applications

Custom bridges when the ERP or in-house software needs a flow that the standard product does not cover.

OpenAPI and HikCentral Professional modules must be confirmed in the concrete environment before committing deliverables.

FAQ

Frequently asked questions about HikCentral API

Based on public Hikvision documentation and our integration experience — without inventing endpoints.

Does HikCentral Professional allow API integrations?

Yes. Hikvision documents HikCentral Professional OpenAPI as an interface for third parties to integrate applications. OpenAPI must be enabled and configured per the manufacturer guide; not every function is available on every deployment.

What is HikCentral Professional OpenAPI?

It is the RESTful interface documented by Hikvision for third parties to integrate applications with HikCentral Professional. It must be enabled per the manufacturer guide; the effective catalog is validated per deployment.

Is “Hikvision API” the same as the HikCentral API?

Not necessarily. “Hikvision API” is a broad term and may refer to different manufacturer products or SDKs. For HikCentral API integration projects we primarily mean HikCentral Professional OpenAPI, not every API in the Hikvision ecosystem.

Can HikCentral be integrated with an ERP?

A frequent project goal: ERP or HR as the source; Onyx for identities and permissions into HikCentral; custom development if needed. We do not offer a generic certified connector for every ERP.

How is HikCentral integrated with HR?

Typically the HR system is the source of people data and the integration publishes or syncs into HikCentral. Design depends on the HR APIs and on the OpenAPI capabilities of the HikCentral environment.

Can HikCentral events be consumed by external applications?

Yes, when the platform publishes those events and the project defines subscription and destinations. Tork is built for that role on HikCentral, with native delivery to Telegram and webhooks/APIs.

What technical requirements should be reviewed before integrating?

HikCentral Professional version, modules and licenses, OpenAPI or other interface status, network/security access to the platform, and the enterprise systems involved. That defines a realistic scope.

Also

Other platforms

If you run Dahua, see our Dahua DSS API integration page.

Dahua DSS API integration →

Need to connect HikCentral with your systems?

Describe your HikCentral Professional environment (OpenAPI), the systems to connect (ERP, HR, or others), and the operational outcome. We assess Onyx, Tork, or a custom integration.

What happens next

  1. 01 We review your inquiry on the same business day
  2. 02 We schedule a call to understand scope and systems
  3. 03 We propose the right integration or product
  • Software · Integration · Physical security
  • Montevideo, Uruguay

Direct contact