Keka Fetch Attendance
Fetch first-in and last-out attendance records from Keka into we360.ai.
Last updated
Was this helpful?
Fetch first-in and last-out attendance records from Keka into we360.ai.
Use this integration to pull attendance records from Keka into we360.ai.
It fetches first-in and last-out punch data. It also maps premise name as location.
This removes manual attendance exports. It keeps attendance data current in we360.ai.
Fetched data appears in:
Daily Attendance Report
All Attendance Reports
Dynamic Reports
The sync runs daily for the previous day. It runs at 05:30 UTC. That is 11:00 AM IST.
You need these values from Keka:
Client ID
Client Secret
API Key
Subdomain
Unique Identification Key
The unique identification key is used to match users. Use the same employee identifier in both systems.
Every synced user must have an Employee ID. If Employee ID is missing, that user will not sync.
Client ID
Unique identifier for API access
API authentication
Client Secret
Secret paired with the Client ID
API authentication
API Key
Key used to authorize API calls
API authentication
Subdomain
Your company Keka subdomain
API base path
Unique Identification Key
Employee identifier used for matching
User mapping
Employee ID
Required employee mapping field
Employee mapping
You must create the credentials in Keka as a Global Admin.
When creating the API key, enable Mark Attendance privileges. Without it, the integration will not work.
we360.ai connects to the Keka API using the saved credentials.
It fetches:
first-in time
last-out time
premise name as location
The integration updates attendance reports after the scheduled fetch completes.
Check the Client ID, Client Secret, API Key, and Subdomain.
Check the unique identification key mapping.
Also confirm the user has an Employee ID.
Confirm the Keka API key has Mark Attendance privileges.
we360.ai integration support — support@we360.ai
Keka API support — support@keka.com
Last updated
Was this helpful?
Was this helpful?