Product Overview
Tipsoi lets you move biometric attendance and access data between your own systems and Tipsoi devices. This guide covers what you can build, how to get access, and how to make your first call — the API reference documents every endpoint in detail.
What you can build
The core idea is simple: get data from Tipsoi into your system — attendance events, enrolments, device state — or push instructions back to a device. There are several ways to connect, depending on where your code runs and how much you want to manage. Pick the one that matches your setup.
Device SDK
One SDK for all Tipsoi, Fastface and Prompt series devices — a single HTTP REST API.
AvailablePull from cloud
Your code calls the HTTP REST API to read attendance and enrolment data on your schedule.
AvailableWe push to you
Receive an event on your server the moment something happens — signed, verifiable webhooks.
Partner-assistedDirect DB write
Tipsoi writes attendance records straight into your database against an agreed schema.
Partner-assistedConnector agent
Run a small Tipsoi agent inside your own infrastructure that pulls from the API and writes where you need it.
Two API surfaces
Tipsoi exposes two related APIs. Most integrations use one or the other; some use both.
| API | What it’s for | Base URL (test) |
|---|---|---|
| Software (HRM) API | Employees, attendance, shifts, rosters, leave, reports — the HR-facing data. | test.clients.inovacetech.com/inovace-client/api/v1 |
| Device Portal API | People, devices, allocations, enrolment and logs — device-level operations. | test.api-inovace360.com/api/v1 |
How it works, end to end
- Get access — Tipsoi issues you API credentials. See Get Access.
- Test in the sandbox — try every endpoint against the test server with safe data before you touch production. See Sandbox.
- Authenticate — exchange your credentials for a JWT bearer token.
- Build — call the endpoints your use case needs. Start with the Quick Start.