Resources / Feocey Open API

Connect with Feocey.

Find the integration reference that matches your device and software configuration.

Clear filters

Resources for your device

FC6825

Display QR and card terminal

Choose where your application runs.

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.

01 / Host integration

Connect an existing platform.

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.

02 / Device development

Build an application on the device.

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 ↗

From reference to a working exchange.

  1. Identify the configuration

    Send the model, firmware version, selected interfaces and the system you want to connect.

  2. Describe one complete interaction

    For example: read a credential, validate it in your platform, return a result and record the event. Include required offline behaviour.

  3. Test with the matching reference

    Review the applicable protocol or SDK, then validate commands, responses, errors and recovery on an evaluation device.

Request an integration reference ↗Product manuals →

Documents for FC6825.

Browse documents for FC6825 →

Common questions for FC6825.

What should I check if serial output is missing or unreadable?

Match the baud rate, data format and electrical interface on both sides, then inspect the cable and any serial-to-USB adapter. Also confirm whether the reader is sending raw content or a framed protocol message before treating additional bytes as corrupted data.

Why can output differ from the original QR content?

A reader in transparent output mode may send the original content, while a protocol or development mode can add a header, length, device information and check data. Select the mode that matches the host application and use the protocol reference for that model and firmware.

Can repeated scans of the same code behave differently?

Yes. Single-read and interval modes can treat repeated presentation of the same code differently, while a different code may still be accepted immediately. Confirm which modes and repeat intervals are available for the selected reader before defining the user flow.

What should I share when choosing a device?

Tell us which credentials people will use, where the device will be installed, which interfaces are required and what should happen in the software workflow. A mounting drawing, host-equipment description or simple process diagram helps us identify the questions that must be confirmed before recommending a configuration.

Does every configuration include the same features?

No. Credential modules, interfaces, mounting parts, network options and software can vary within the same product family. Confirm the exact model and selected options in writing before designing an enclosure, cable set or integration around it.

Browse questions & answers →
← All resources