Purpose
The Keka Fetch Attendance Records integration allows first-in and last-out punch data from Keka to be automatically retrieved into we360.ai and made available in the Daily Attendance Report section.
This eliminates the need for manual data export and ensures that employee attendance is always up to date.
Data is fetched daily from Keka the next day at 5:30 UTC (11:00 AM IST).
Section 1 >
Base Requirements
we360.ai Field | Description | Keka Usage |
Client ID | Unique identifier for API access | API authentication |
Client Secret | Secret key paired with Client ID | API authentication |
API Key | Key to validate and authorize API calls | API authentication |
Subdomain | Your company’s unique Keka subdomain | API base path |
Unique Identification Key | Employee identifier for matching records | User mapping |
Employee ID | Must be filled for successful sync; missing IDs will prevent sync for that user | Employee mapping |
Section 2 >
Generating API Credentials in Keka
Purpose:
The Keka API credentials (Client ID, Client Secret, and API Key) allow we360.ai to securely fetch attendance data from Keka.
Important:
✅ While creating the API key in Keka, ensure that "Mark Attendance" privileges are enabled.
Steps:
Log in as a Global Admin to the Keka Admin Portal.
Navigate to: Global Admin Settings (1) → Integrations & Automation (2).
Select API Access (3).
Go to the API Key (4) section.
Generate your Client ID and Client Secret (5).
Only the Global Admin can generate and manage API keys.
To create a new API Key:
Click Create New Key (6).
(Optional) Enable Set Expiry toggle (1) and choose an expiry date.
Ensure Attendance privileges are selected.
Click Save (2) to store your credentials.
Section 3 >
Steps in we360.ai
Obtain API credentials from Keka (from Section 2 above).
Go to Keka Fetch Attendance settings in we360.ai.
Enter the following:
Client ID
Client Secret
API Key
Subdomain – Example: If your Keka URL is
https://company.keka.com, entercompany.Unique Identification Key – Employee ID or mapping field.
Enable Auto-Run by selecting the checkbox.
Save the integration.
Note: The Employee ID field is mandatory for a successful sync. If left empty, the sync will fail for that specific user.
Section 4 >
Integration Flow
we360.ai connects to Keka API using stored credentials.
The system fetches first-in and last-out times for each employee.
Data is updated in All Attendance Reports in we360.ai.
Fetch occurs daily for the previous day’s data at 5:30 UTC (11:00 AM IST).
Section 5 >
Troubleshooting
Issue | Possible Cause | Resolution |
Attendance data not appearing in we360.ai | Incorrect API credentials | Verify Client ID, Client Secret, API Key, and Subdomain. |
| Missing Unique Identification Key | Check Employee ID mapping in we360.ai. |
| API key missing required privileges | Ensure "Mark Attendance" privilege is enabled in Keka. |
Section 6 >
Support
we360.ai Integration Support: [email protected]
Keka API Assistance: [email protected]