Particularities of Control iD's Terminals

The API described in this document applies to all Control iD access control devices, but some of the functions described here will only apply to certain products. This topic aims to describe in a general way the particularities of each product, what is not a particularity of some product, will apply to all others.

iDAccess and iDFit

In these products, the action to open the doors is "door". More details in Remote Door and Turnstile Opening. The event generated by the monitor to report that the door was opened will be notified by the endpoint hostname:port/api/notifications/door

iDBlock

In this product, the action to allow the turnstile to turn to one side is "catra". More details in Remote Door and Turnstile Opening. The event generated by the monitor to report turns on the turnstile will be notified by the endpoint hostname:port/api/notifications/catra_event

iDBox

In this product, the action to open the doors is "door" and it has 4 (four) portals in total. More details in Remote Door and Turnstile Opening. The event generated by the monitor to report that the door was opened will be notified by the endpoint hostname:port/api/notifications/door

iDFlex, iDAccess Pro and iDAccess Nano

In these products, the action to open the doors is "sec_box". More details in Remote Door and Turnstile Opening. The event generated by the monitor to report that the door was opened will be notified by the endpoint hostname:port/api/notifications/secbox

iDFlex and iDAccess Nano

In these products, to enable enterprise mode, it will be necessary to do an upgrade process as described in upgrade.

iDUHF

In these products, the action to open the internal relay is "door" and to open the external relay (MAE) is "sec_box". More details in Remote Door and Turnstile Opening. The event generated by the monitor to report that the internal relay was opened will be notified by the endpoint hostname:port/api/notifications/door and the event generated by the monitor to report that the external relay was opened will be notified by the endpoint hostname:port/api/notifications/secbox

iDFace

In this product, the action to open the ports is "sec_box". More details in Remote Door and Turnstile Opening.

In the iDFace, it is possible to configure the period between relay activations while the recognized user remains in front of the device. Just send a set_configuration request (Change Settings) while modifying the max_identified_duration parameter of the face_id module to the desired interval in milliseconds. It is not recommended to apply values below the range in which the relay keeps open. When the parameter is set to zero, the relay will not open periodically, requiring the user to leave the front of the camera and wait for the streaming to end for a new identification and door opening.

It is also possible to set iDFace to turn the screen off when idle. This can be done by changing the screen_always_on parameter to "0", making the screen turn off until someone appears in front of the display or touch the screen. To keep the screen always on, just leave the parameter at "1". You can do this with a set_configuration request (Modify-configurations).

Limitation on the number of templates

The number of templates (fingerprints) that can be stored on the device (in standalone and contingency mode):

• iDAccess, iDFit, iDBlock: 2000 templates;
• iDFlex, iDAccess Pro, iDAccess Nano: 6000 templates;