Issue with the VAPIX Library on Axis A1610 Controllers with Axis Camera Station Secure Entry (v12.x)

[alevilla86]

Hi everyone,

I recently joined the development team responsible for integrating our platform with Axis devices, mainly to manage credentials, card holders, groups, schedules, and to query event logs (e.g., determining which card holder accessed which door and when). Our system complements Axis's native functionalities, allowing technicians to make configurations directly from Axis UIs in case of internet outages.

Until now, we had successfully worked with A1001 controllers using the VAPIX library to interact with the devices. However, as we migrate to A1610 controllers, we are encountering significant issues due to differences in the operating systems:

• Axis OS (v10.x): VAPIX works as before, but it lacks a UI for configuring access (card holders, schedules, etc.), which is a critical requirement for us.

• Axis Camera Station Secure Entry (v12.x): This version includes a UI that meets our needs but seems to lack a functional VAPIX library.

According to Axis's official documentation, VAPIX is still supported in version 12.x (https://help.axis.com/en-us/axis-os#changes-in-axis-os-12). However, when I try to use it (e.g., with the URL https://{{HOST}}/vapix/schedule -d '{"axsch:GetScheduleList":{}}'), I always get a 404 error stating that the URL was not found on the server.

My questions for the community are:

• Was there any change in the path or method for accessing the VAPIX library in version 12.x?

• Has anyone successfully used VAPIX with A1610 controllers managed through Camera Station 5?

• If VAPIX is no longer usable in this version, is there any alternative for integrating advanced functionalities (schedule management, credentials, event logs) without losing the UI provided by this operating system version?

Any guidance or experience would be greatly appreciated. Thanks in advance!

[github-actions[bot]]

This automatically generated reply acts as a friendly reminder.

Answers to your questions will most often come from the community, from developers like yourself. You will, from time to time, find that Axis employees answers some of the questions, but this is not a guarantee. Think of the discussion forum as a complement to other support channels, not a replacement to any of them.

If your question remains unanswered for a period of time, please revisit it to see whether it can be improved by following the guidelines listed in Axis support guidelines.

[vivekatoffice]

Hi @alevilla86 ,

This thread may help :849

[alevilla86]

Thank you, I understand. Now, why VAPIX is not working when I update the firmware version to 12.X? I can't understand why in the documentation from Axis on v12.X (https://help.axis.com/en-us/axis-os#changes-in-axis-os-12) they mention VAPIX as if it's there, but I can't manage to make a single request to the VAPIX endpoints.

[vivekatoffice]

Hi @alevilla86 ,
I checked with the Axis PACS team for this. The Axis OS 12.X do support the other VAPIX APIs (example /axis-cgi/apidiscovery.cgi) but not the PACS APIs in VAPIX. 😕

They do have a plan for the improvement of the second generation of PACS APIs and will be available for the Axis Technology Integration Partner Program members in future.

I can confirm that integration using the APIs available here is the only way now(AXIS OS version 10.12.256.1) for partners/developers to work with Axis network door controllers.

[alevilla86]

I understand. So, for A1610s working with an NVR (v12.X) is not possible to manage physical access control via VAPIX.

Could it be done through the Axis Camera Station 5 API? i.e. "https://%s/Acs/Api/CameraListFacade/GetCameraList", "https://%s/Acs/Api/RecordingFacade/GetRecordings" and so on?

I haven't found any documentation related to the AxisCameraStation (ACS) API, but I know it exists. Is there a way to manage the cardholders, schedules and groups using this API?

[vivekatoffice]

Hi @alevilla86 ,
AXIS Camera Station API offers minimal (like opening a door with action button) functionalities related to the AXIS Camera Station Secure Entry.

Verified with May 30, 2024 (Rev. 2.31)

References:

Integration of third-party products

AXIS Camera Station API

Hi @alessandroFerraioliLeonardo.

Unfortunately the access to documentation and development support for AXIS Camera Station integration interfaces and tools are available to selected partners only. I think you need to contact your Axis account manager to initiate a discussion regarding this topic.

[alevilla86]

Thank you for your answers, they were really helpful to understand our current options.

[qcastel]

Hi @alevilla86 👋,

I saw your earlier comments in this thread about trying to use the VAPIX API on an A1610. I’ve tried something similar myself:
• Downgraded to AXIS OS Version 10.12.288.1 (expected to include VAPIX access control)
• Checked /axis-cgi/apidiscovery.cgi

However, when inspecting apiList, none of the access control APIs appear (no pacs, access-control, cardholder, door, etc.). Only generic APIs such as network-settings, user-management, io-port-management, mqtt, event streaming, etc. are present.

Because of this, all physical access control endpoints return 404.

Have you managed to find a version or configuration of firmware where the Access Control / Physical Access API actually shows up in the discovery list and works for creating credentials, cards, pins, schedules, etc.?

I’d really appreciate any insight — I’m trying to do the same thing on A1610 and haven’t been able to get the PACS API to show up.

Thanks!

[alevilla86]

Hi @qcastel , it's been a while but at the end we couldn't find a version that meet our needs. We ended up replacing our Axis controllers for Unifi controllers :(

[qcastel]

@alevilla86 Thanks for your answer! I spend a couple of hours looking at unifi. Looks pretty net. Are you happy with your choice? Would you recommend it?