Greythr calls it gross_salary. Darwinbox calls it ctc_breakup. SAP buries it three levels deep in a payroll object with a field name no one outside their implementation team recognises.
The moment your product needs employment data from more than one source, you have a choice: build and maintain a custom integration for each one, or stop scaling
Weeks per connector
Each HRMS integration takes weeks to build and forever to maintain
Silent breakages
Rate limits, pagination, retry logic - reinvented per connector
Reinvented plumbing
Vendor API changes break pipelines silently, discovered downstream
New HRMS, new sprint
New customer, new HRMS, new sprint
A Unified API sits between your product and every HRMS and payroll system your customers' employers use.
You integrate once. You get a single, consistent endpoint. The Unified API handles authentication, schema translation, sync scheduling, and error recovery for every provider underneath - invisibly, permanently.
Your product sees one data model. Always.
The problem with employment data
TartanHQ's Unified API is built specifically for India's HRMS and payroll ecosystem - 100+ systems, from Greythr and Darwinbox to SAP SuccessFactors and Oracle HCM, all returning data in a single normalised schema.
1
One Data Model
One data model across every provider Employee master data, payroll structure, org hierarchy, and employment events - consistent field names, consistent types, consistent response shape. Whether the employer runs Keka or Workday, your API call looks identical and your response looks identical.
2
Read & Write
Bi-directional Read employment and payroll data from the source. Write back into it - deduction instructions, onboarding triggers, roster updates - through the same integration. No separate connector for write operations.
3
Live Event Stream
Real-time event stream Subscribe to employment events by type. Joiner, exit, promotion, salary revision - pushed to your endpoint the moment the record changes in the source HRMS, not on your next poll cycle.
4
Custom Field Access
Custom fields and passthrough Surface employer-specific data that sits outside the standard schema - grade bands, cost centre codes, custom HR fields. Or make a direct passthrough call to the underlying provider when you need raw access.
5
Scale-Ready Infrastructure
Built for scale Rate limits, pagination, retries, webhook throttling - handled by TartanHQ infrastructure, not your engineering team.
Four canonical objects. Same structure regardless of source.
Employee
Identity, designation, department, date of joining, employment status, reporting structure, contact details.
Payroll
Payroll Gross, net, basic, HRA, allowances, deductions, PF, TDS - broken down by salary head, per pay period, directly from payroll.
Organisation
Organisation Company structure, cost centres, business unit hierarchy, headcount bands, employer identity.
Employment Events
Employment Events Joiner, exit, promotion, salary revision, transfer - timestamped, typed, and pushed as they occur in the source system.
Every connector built, maintained, and monitored by TartanHQ. When a vendor updates their API, we update the connector.
ISO 27001
ISO 27701
AICPA
CISA
