Timestamp API records
Use Timestamp API Records to see the raw check-in and check-out punches that turnstiles, biometric systems such as ZKBioTime, file uploads and other integrations send to KAMI, and whether each one made it onto an attendance event. It is the page to open when a person clocked in at the gate but their day in KAMI shows no check-in.
Where: Attendance › Tools & Reports › Timestamp API Records, under Check-ins & devices
You need: the Attendance Manager right. You see only the people your access covers.
This report covers punches from integrations only. Check-ins made in the KAMI app, on ClockSmart or on the web are not listed. For those, see Check-in error and GPS mock reports.
How to find a punch
- Go to Attendance › Tools & Reports and open Timestamp API Records. It opens on the last 7 days.
- Set the date range.
- Select Filters and choose what the dates apply to under Type: Timestamp (when the punch happened) or Created (when KAMI received it).
- In Filters, choose Check-ins only or Check-outs only if you need one direction, and With error to see only punches that failed.
- Set Local Branch Time to show times in a branch's timezone rather than your own.
- Use Search for the person's name or employee ID.
- Select the eye icon under Matched Event to open the event the punch was applied to.
- To keep a copy, select Export, then Microsoft Excel (.xlsx). The file is built in the background and sent to you.
What each column shows
| Column | What it shows |
|---|---|
| Employee | The person, with their position. If the employee ID sent did not match anyone, the ID shows with a warning |
| Department | Their department |
| Event Date and Time | When the punch happened |
| Check-in/out | Checked In or Checked Out |
| Matched Event | The start time of the event the punch was applied to. Deleted means that event has since been deleted |
| Import Date | When KAMI received the punch |
| Status (Processed/Error) | A spinner means it is waiting to be processed. A red cross means it failed: hover to see why. Blank means it was applied |
How punches are applied
KAMI processes waiting punches every minute. For each one it finds the employee by employee ID, then the event the punch belongs to, and writes the time onto that event's check-in.
- The first check-in of an event is the one that counts. Later check-ins do not move it.
- A later check-out replaces an earlier one, so the last check-out of the day is the one that counts.
- A check-in after a check-out clears the check-out, for someone who left and came back.
- A ZKBioTime check-out never overwrites a check-out recorded some other way, such as in the app.
The errors
| Error | What to do |
|---|---|
| Could not find employee. | The employee ID sent does not match a profile. Fix the ID in KAMI or in the other system |
| Could not match to an event. | The person has no event at that time. Add the missing schedule, then have the punch sent again |
| This is a check out timestamp, but event has no check in timestamp. Ignoring. | The check-in never arrived. Find it, or correct the day by hand |
| Check out timestamp is somehow before check in timestamp | The two punches are the wrong way round, often a clock problem on the device |
| Cannot record check out because the event's break was never closed. Ignoring. | Close the break on the event, then correct the check-out |
What Happens Next
An applied punch updates the event straight away, and from there the Timesheet and payroll. A failed punch changes nothing, so that day stays without the time until someone corrects it. See Correcting attendance.
⚠️ Records are deleted after 30 days. Export anything you need to keep, such as evidence for a dispute, before then.
Tips
- Filter With error once a week. Errors here never reach the employee, so nobody else will notice them.
- Many "Could not find employee." errors usually mean employee IDs differ between KAMI and the other system. Fix them at the source.
- Many "Could not match to an event." errors usually mean schedules are missing for those people.
- Set Local Branch Time when your branches are in different timezones, so the times match what the gate shows.
Troubleshooting / FAQ
Q: A punch has a spinner for a long time. It is waiting to be processed. That normally takes about a minute. If it stays, contact support.
Q: The person clocked in at the gate but the punch is not listed. It never reached KAMI. Check the integration or device on your side.
Q: The matched event says Deleted. The punch was applied, but the event was deleted afterwards. Check the Event Tracker to see who deleted it.