Device connection
Confirm TCP/IP, Wi-Fi, USB or other network options for the selected model and installation.
SDK & API
Define the integration boundary before requesting an SDK package.
Start with the device model, firmware, operating mode, required events and offline behavior. TIMY can then match the appropriate documentation and sample project.
Integration method
Model, firmware and software mode come first.
A protocol name alone does not confirm a complete integration. The project should define how devices connect, which records move, how doors are controlled and what happens when the network is unavailable.
Java SDKPHP SDKC# SDKTCP/IPWiegandOSDP
01 · Select model02 · Confirm firmware03 · Define data flow04 · Test sample device
Evaluation checklist
Six areas to confirm with the integration team.
This checklist helps distributors and software partners prepare a useful technical request.
Door and controller
Confirm lock output, exit button, alarm, Wiegand or OSDP roles against the access architecture.
Application data
Define people, credential, event, attendance, visitor and device-management data required by the project.
Offline operation
Confirm local verification, record capacity, synchronization rules and conflict handling by device and software mode.
Security and privacy
Review authentication, transport security, biometric storage settings and customer deployment policy.
Version compatibility
Match the SDK, protocol and sample project to the production model and firmware version.
Published capability scope
Integration options described in the 2026 catalog.
Availability still depends on model, firmware and deployment mode. TIMY should confirm the applicable package before development begins.
SDK languages
The 2026 TIMY catalog states Java, PHP and C# SDK support for integration projects.
WebAAS local deployment
The catalog describes browser-based local management on Windows with a built-in database and multilingual support.
OSDP roles
Supported TIMY face terminals can operate with OSDP controllers or OSDP readers, subject to model configuration.
BioSecureCard
The catalog presents an encrypted CPU-card option where biometric data is stored on the card rather than an external server.
Yunatt functions
Published functions include attendance, access control, visitor QR, field attendance, elevator access and video intercom management.
Device browser access
Selected WebAAS workflows provide LAN browser access to device-management functions.
What to send
A useful SDK request is specific.
Include the following information so the technical team can identify the right package and test path.
1Device model and quantity
2Current firmware version
3Target operating system and language
4Required event and user fields
5Door, controller and network topology
6Offline and synchronization expectations
Project evaluation
Prepare an integration request for TIMY engineering.
Share the door count, user count, credential mix, installation environment and software requirement. TIMY will help narrow the product and integration path.