Integration Description
The Keka integration connects Zapro AI to the Keka employee directory through the Keka REST API, so employees, departments, cost centers, locations and reporting managers become the requesters, approval routes and spend coding used across purchasing and accounts payable in Zapro AI.
What the Keka integration does
- Approval routing without a matrix to maintain
- Invoices arrive already coded
- Access matches the roster
How your records stay in sync
Skip the double entry. Zapro AI keeps these records matched with Keka, so no duplicates are created and your data stays centralized.
How the connection is set up
- Create an API client in Keka
- Exchange the credentials for a token
- Agree the attributes in scope
- Clean the cost center list first
- Run one department end to end
How teams use it
- StartupEmployees become requesters with limits and a named approver, so routine purchases clear without the founder and larger ones still reach them.
- SMBThe requester's cost center codes the request at creation and carries through to the invoice, so the accounts team posts rather than reallocates.
- EnterpriseThe Indian entities load from Keka with their own approval thresholds, other regions load from their own sources, and group spend reporting stays in one place.
How Zapro AI works with Keka
Procurement
Creates purchase requests from Keka employees and routes them by manager, cost center and value.
AP Automation
Captures supplier invoices, extracts the lines and matches them to the purchase order and receipt.
Spend Analytics
Reports spend by cost center, department and location using the values Keka maintains.
Vendor Management
Onboards vendors with templates and keeps their compliance documents and performance in one profile.
Zapro made procurement effortless with a user-friendly interface and stellar support. Our team and suppliers adapted quickly, and we're now seeing faster approvals and smoother collaboration.
Questions teams ask
How do you connect Keka to procurement software?
Through the Keka REST API. An administrator creates an API client in Keka and shares the client id, client secret and API key, which the procurement platform exchanges for an access token on the tenant token endpoint. Zapro AI reads employees, departments, cost centers, locations and reporting managers on a schedule, and a scheduled employee file over SFTP covers tenants where API access is not enabled.
Does Keka handle purchase approvals?
Keka approves HR items such as leave, attendance regularization and expense claims. It does not check a purchase order, a budget or a supplier contract. Zapro AI runs the spend approval and uses the Keka reporting line to decide who it goes to.
What data is read and how is it protected?
Identity and organizational fields only: employee number, name, official email, job title, reporting manager, department, cost center, location and status. Salary, attendance and statutory data stay out. Credentials are stored encrypted, data is encrypted with AES-256, access follows role permissions, and every sync is written to the audit trail.
Can expense claims stay in Keka?
Yes. Employee reimbursements can carry on in Keka while vendor purchasing, orders and supplier invoices run in Zapro AI. Keeping the two separate avoids the usual argument about which system owns a claim.
What if an employee has no cost center?
They are created as a requester but their requests land in a holding dimension that finance must code before approval. It is visible rather than silent, which is why the cost center clean up belongs before the first sync.

