Hanwha Vision SUNAPI and Open Platform
SUNAPI provides device access, while Open Platform supports applications on compatible Hanwha devices. Check firmware, supported operations and deployment requirements.
Sources and scopeSource record 25 August 2026
Technical source record: 25 August 2026. Check the linked documentation for current product requirements.
Public Hanwha Vision product and STEP pages establish the surfaces; current complete SUNAPI/Open Platform packages, universal version claims, model matrices, operations, authentication, and licences are excluded where login gated.
On this page
Overview#
Vendor APIs / Device and edge video / Hanwha Vision
Hanwha Vision documents SUNAPI as a native HTTP API family and distributes related SDK material through its STEP partner/support environment. Open Platform is the separate on camera application framework for supported models. Public product pages often identify which of these are present; the exact guide and SDK package remain the implementation authority.
Documented interface map#
| Surface | Purpose | Access/evidence boundary |
|---|---|---|
| SUNAPI HTTP API | Native device integration for supported cameras, recorders and access products | Model pages and STEP catalogue public; exact operation and version guide can require STEP login |
| SUNAPI SDK | Vendor development package for supported integration workflows | Distributed through STEP download/support routes; package compatibility must be pinned |
| Open Platform SDK | Builds applications that execute on compatible Hanwha network cameras | Public overview; SDK, model/firmware/toolchain and resource contract through STEP |
| ONVIF profiles | Standards based media/device interoperability on conformant models | Separate from SUNAPI and Open Platform; use exact declaration/model support |
Version evidence#
On 25 August 2026, the STEP technical support page listed a SUNAPI v2.6.8 access control API guide dated 9 April 2026. That is evidence for the named access control document only. It must not be described as the universal latest SUNAPI for cameras, recorders or every region.
Public camera product pages reviewed for this catalogue listed combinations of ONVIF, SUNAPI HTTP API and Open Platform. Availability varies by model and firmware. Capture the product page, firmware release note, API guide revision and SDK package manifest in the project inventory.
Choosing a surface#
- Use declared ONVIF profiles when the required cross vendor feature is standardised and conformant.
- Use SUNAPI when an officially documented native capability is required and the exact device exposes it.
- Use the SUNAPI SDK when the vendor package provides supported higher level media/event/device behaviour that a direct HTTP integration shouldn't reproduce.
- Use Open Platform only for logic that genuinely must run at the edge and fits the device’s supported application and resource model.
Do not choose a legacy ActiveX integration from an old example without current vendor support evidence. The historical STEP FAQ cited here is no longer available at its former address; obtain current SDK and migration guidance through the STEP partner portal.
Authentication, events, and commands#
Take authentication, HTTPS, certificate, role and session behaviour from the exact current guide and firmware. Product pages advertising HTTPS or security properties are capability evidence, not a universal auth contract. Provision a unique least privileged account and don't accept plaintext fallback or permanent certificate exceptions.
For events, document subscription/stream framing, heartbeat, reconnect, duplicate/gap behaviour, source timestamps and schema version. For media, pin profile, codec, transport, session lifetime and concurrent stream limits. For access control, PTZ, audio, I/O, restart, firmware and configuration operations, require separate authorisation and post operation reconciliation.
Open Platform boundary#
An on camera application can affect availability, privacy and evidence. Before deployment, verify:
- compatible camera models, firmware, architecture and SDK/toolchain;
- application signing/approval and distribution route;
- documented APIs and permissions;
- CPU, accelerator, memory, storage, process and network limits;
- start/restart behaviour and coexistence with recording/analytics;
- secure secret storage, update, rollback and removal;
- support policy when multiple third party applications share a device.
Never use an undocumented operating system interface simply because it is visible inside an application environment.
Lifecycle and compatibility#
STEP has regional/localized portals and account controlled downloads. Recheck the correct region, product family, document date, licence and firmware release before implementation. Keep restricted packages and documents under their portal terms.
Primary sources#
- Hanwha Vision STEP technical support, official document catalogue and dated access control SUNAPI guide evidence.
- STEP partner portal, current entry point for partner support. The old Download Center, Open Platform and FAQ addresses returned 404 on 29 September 2026; their historical content has not been revalidated at this new entry point.
- Example Hanwha camera product page, model level API/profile declarations; don't generalize to other products.