Resources / Feocey Open API
Find the integration reference that matches your device and software configuration.
Feocey Open API is the starting point for device integration guidance. Protocols and references are matched to the hardware, firmware and application; there is no single public endpoint catalogue covering every model.
Your access, attendance or visitor platform exchanges commands and events with the selected device. Start with the required data, connection method and device firmware.
Face terminals, QR readers and controllers use different interfaces and message formats. An Ethernet or RS485 connection alone does not define the API.
On supported DejaOS models, develop the device interface and behaviour in JavaScript. Match the SDK and available modules to the selected hardware configuration.
The DejaOS documentation describes device application development. A project’s host protocol and service credentials are separate parts of the integration.
Read DejaOS documentation ↗Send the model, firmware version, selected interfaces and the system you want to connect.
For example: read a credential, validate it in your platform, return a result and record the event. Include required offline behaviour.
Review the applicable protocol or SDK, then validate commands, responses, errors and recovery on an evaluation device.
Not necessarily. Identity enrollment and access permission are separate steps in many systems. Confirm that the person, credential, target device, schedule and permission group have been linked and that the authorization was delivered successfully.
No. A device can have local network access without maintaining its platform or messaging connection. Check the physical network, IP settings and service connection separately, using the indicators or logs available for the selected system.
Compare the RS485 wiring, polarity, grounding and communication settings with the instructions for both devices. Then confirm the reader output mode and controller input configuration; a correct cable cannot compensate for mismatched communication settings.
Identity verification, access permission and the physical control output are separate parts of the workflow. Have a qualified installer check the operating mode, permission result, relay timing, controller output and lock wiring against the installation instructions.
Confirm the overseas model and device identifier registered in the platform, including letter case and similar-looking characters. Then check connection stability, the expected firmware and whether the command is intended for that operating mode.
Allow Google Analytics to help us understand traffic sources, page visits, submitted inquiries, document clicks, email-link clicks and visits to Alibaba or WhatsApp. We do not send your name, email or inquiry message to Analytics.
Analytics stays off until you allow it. Your choice does not affect inquiries or videos you choose to play. You can change it here at any time.
Current choice: not selected.
Read the website privacy notice