Device

The Device module allows you to securely connect external hardware devices and third-party applications with InstiKit.

Each registered device receives a unique Authentication Token (Auth Token) that can be used to authenticate API requests. This enables external systems to securely exchange data with InstiKit without requiring a user account.

Why Use Devices?

Many educational institutions use external systems alongside their ERP.

Examples include:

• Biometric attendance devices
• RFID attendance systems
• QR code scanners
• Library kiosks
• Smart gate systems
• Face recognition systems
• Payment terminals
• Custom mobile applications
• Third-party software integrations

Instead of sharing user credentials, these systems authenticate using a secure device token.

Adding a Device

To register a new device:

1. Open User Menu → Device.
2. Click Add Device.
3. Enter a unique device name.
4. Enter a device code.
5. Optionally provide a description.
6. Save the device.

After saving, InstiKit automatically generates an Authentication Token (Auth Token) for the device.

Device Information

Each device contains:

• Device Name
• Device Code
• Description
• Authentication Token
• Created Date

The generated authentication token uniquely identifies the device when communicating with the API.

Authentication Token

Every registered device receives a secure Authentication Token.

The token is used when making API requests to InstiKit.

Instead of authenticating with a username and password, the external application simply sends its authentication token with every request.

This provides a secure and simple way to integrate hardware and software with the ERP.

Example Workflow

A typical biometric attendance integration works as follows:

1. Register the biometric device in InstiKit.
2. InstiKit generates an Authentication Token.
3. Configure the token in the biometric synchronization software.
4. The device sends attendance records to the InstiKit API.
5. InstiKit verifies the token.
6. If the token is valid, the attendance data is processed and stored.

The same approach can be used for any external integration supported by the API.

Security

Authentication tokens should be treated like passwords.

Only share the token with trusted applications or devices.

If you believe a token has been exposed or compromised, update or regenerate the device credentials immediately and reconfigure the connected device.

Supported Integrations

The Device module can be used for integrations such as:

• Biometric attendance machines
• RFID readers
• QR code scanners
• Face recognition systems
• Smart gate controllers
• Mobile applications
• Desktop applications
• Custom middleware
• Third-party ERP integrations

Future integrations can also use the same authentication mechanism without requiring changes to user accounts.

Frequently Asked Questions

Do devices require a user account?

No. Devices authenticate using their Authentication Token and do not require a user account.

Can multiple devices be registered?

Yes. You can register as many devices as required. Each device receives its own unique authentication token.

Can different devices use the same token?

No. Every device has its own unique authentication token, allowing each integration to be managed independently.

Can the authentication token be used with InstiKit APIs?

Yes. The generated authentication token is intended to authenticate supported API requests for securely sending or retrieving data.

Related Documentation

• API
• QR Code Attendance
• Attendance