Attendance API: Full attendance entries management

What's new

You can now manage attendance entries end-to-end via the Bob Public API, including create, update, search, and delete operations. This also introduces dedicated clock-in / clock-out endpoints, enabling real-time, API-driven attendance flows (for example, kiosk or on-site check-in scenarios).

Why this matters

If your integration relies on Bob as the system of record for attendance, you can now:

• Create entries from an external system
• Update entries for corrections and completion (for example, add clock-out later)
• Fetch entry IDs via search, then update/delete reliably
• Associate entries with projects and tasks for project-based reporting
• Support real-time clock-in/out flows, such as kiosks, mobile apps, or physical terminals

Unlike standard entry creation, clock-in / clock-out endpoints are optimized for incremental, real-time updates. For example, a kiosk flow typically creates an entry at clock-in and completes it later at clock-out, rather than sending a full entry upfront.

Additionally, the API now supports timezone-aware attendance handling, ensuring entries are recorded and interpreted correctly across distributed teams and global workforces. This is especially important for integrations operating across multiple regions or syncing data from systems in different timezones.

New endpoints

• Fetch attendance entries
• Bulk create attendance entries
• Bulk update attendance entries for an employee
• Clock in (create entry)
• Clock out
• Delete an attendance entry

To learn more, see Explore Attendance API.

Action required

• This is a new capability. No action is required unless you want to adopt it.
• This expands on the existing Import punches endpoint (still supported), by enabling full lifecycle management of attendance entries, including clock in, clock out, and linking entries to projects (when policies allow).