Home Integrations Keka HRIS Integration with Peoplebox

Keka HRIS Integration with Peoplebox

Last updated on Jun 19, 2026

This guide walks you through connecting your Keka account to Peoplebox, enabling employee data to stay automatically synchronized between the two systems.

1. Overview

The Keka integration allows Peoplebox to pull your employee directory directly from Keka. Once connected, Peoplebox periodically syncs employee profiles, keeping headcount, reporting structures, departments, and other employee attributes up to date without the need for manual CSV uploads.

2. Data synced from Keka

Peoplebox syncs the following employee attributes from Keka: Employee ID (Employee Number), Full Name (Display Name), Email (Work Email), Job Title, Department, Business Unit, Manager, Date of Joining, Date of Exit, Gender, Employment Type, Location, Phone Number, and Profile Picture. These fields are automatically updated during each sync to help keep employee records in Peoplebox accurate and up to date.

Note: Employees without a valid work email address are not synced, as email is required to identify and match employee records.

3. Prerequisites

Before setting up the Keka integration, ensure the following requirements are met:

  • You have admin access to your Keka account.

  • The Keka API feature is enabled for your organization. If you are unsure, please contact Keka Support.

  • You have generated the required API credentials from the Keka Developer/API settings, including:

    • Client ID (client_id)

    • Client Secret (client_secret)

    • API Key (api_key)

4. Getting Your Keka API Credentials

To connect Keka with Peoplebox, you will need to collect the required API credentials from your Keka account.

  • Log in to your Keka admin portal.

  • Navigate to Settings → Integrations → API Access (or Developer Settings, depending on your Keka version).

  • Generate or copy the following credentials:

    • Client ID

    • Client Secret

    • API Key

  • Note down your Keka domain name, which is the subdomain in your Keka URL. For example, if your URL is yourcompany.keka.com, the domain name is yourcompany.

Note: Keka access tokens expire every 24 hours. Peoplebox automatically refreshes the access token before each sync, so no additional action is required after the integration is configured.

5. Setup Steps (Peoplebox Admin)

Share the following details with your Peoplebox account manager or Peoplebox Support to complete the integration setup:

  • Client ID (client_id) – OAuth Client ID generated in Keka.

  • Client Secret (client_secret) – OAuth Client Secret generated in Keka.

  • API Key (api_key) – API Key generated in Keka.

  • Keka Domain Name (keka_domain_name) – Your Keka subdomain (for example, yourcompany from yourcompany.keka.com).

  • Admin Email ID (admin_email_id) – The email address of the Keka administrator authorizing the integration.

Once these details are shared, the Peoplebox team will configure the integration and trigger an initial employee sync.

6. How Sync Works

  • Sync Frequency: Peoplebox syncs employee data from Keka on a scheduled basis (by default, once daily).

  • Directory Coverage: Employee records are fetched in batches to ensure the complete directory is synced, including support for large organizations.

  • New Employees: Employees added in Keka are automatically created in Peoplebox during the next sync.

  • Employee Updates: Changes made in Keka, such as updates to job title, department, manager, or other employee details, are reflected in Peoplebox after the next sync.

  • Employee Exits: When an employee's status is marked as Relieved and the exit process is Completed in Keka, the employee is marked as inactive in Peoplebox, and the exit date is synced accordingly.

7. Field Mapping Details

Some fields in Keka use internal values that are mapped to user-friendly values in Peoplebox during the sync process.

Gender: Keka stores gender as a numeric value. These values are mapped in Peoplebox as follows:

  • 1 → Male

  • 2 → Female

  • 3 → Non-binary

Employment Type: Keka stores employment type as a numeric value. These values are mapped in Peoplebox as follows:

  • 1 → Permanent

  • 2 → Contract

Department and Business Unit: Keka uses a Groups structure to organize employees. During the sync:

  • Group Type 1 is mapped to Business Unit.

  • Group Type 2 is mapped to Department.

8. Frequently Asked Questions

  • Will existing employees in Peoplebox be affected?
    Ans: The sync updates employee records that match by email address. New employees found in Keka are added automatically, while existing employee records are updated with the latest information from Keka.

  • What happens if an employee does not have a work email address in Keka?
    Ans: Employees without a work email address are skipped during the sync process. To ensure all employees are synced correctly, make sure every active employee has a valid email address in Keka.

  • Can I trigger a manual sync?
    Ans: Yes. If you need a sync outside the regular schedule, please contact Peoplebox Support.

  • Is our Keka data secure?
    Ans: Yes. Integration credentials are stored securely, and API access tokens are generated as needed during the sync process rather than being stored long-term.

  • What happens if my Keka API credentials change?
    Ans: If your Keka API credentials are updated or revoked, please contact your Peoplebox account manager or Peoplebox Support to provide the new credentials. Syncing will resume once the updated credentials have been configured.