Unified API
One API contract. Every HRMS and payroll system in India.
Build once against Tartan to read, write and subscribe to employee and payroll data from 100+ HRMS and payroll systems. It’s the same API that powers HyperSync and every Tartan AI coworker.
GET /v1/employees/EMP-1042 x-employer: acme-finserv x-connection: keka
{
"id": "EMP-1042",
"name": "Priya Menon",
"designation": "Credit Manager",
"employment_status": "active",
"date_of_joining": "2021-04-12",
"payroll": { "gross": 184000, "currency": "INR" }
}
The Problem
Every new HRMS is another sprint your team didn’t plan for.
The moment your product needs employment data from more than one source, you choose between building a connector for every HRMS or slowing down. The build is the cheap part. The upkeep never stops.
Weeks per connector
Each HRMS integration takes weeks to build and forever to maintain.
Silent breakages
Vendor API changes break pipelines quietly, and you find out downstream.
Reinvented plumbing
Rate limits, pagination and retry logic, rebuilt for every connector.
New HRMS, new sprint
New customer, new HRMS, new sprint. Your roadmap waits.
Keka
Darwinbox
greytHR
SAP SuccessFactors
Workday
Zoho People
Oracle HCM+ 90 moreWhat a Unified API does
One layer between your product and every provider.
1
Sits in the middle
A Unified API sits between your product and every HRMS and payroll system your customers’ employers use.
2
You integrate once
One consistent endpoint. Tartan handles authentication, schema translation, sync scheduling and error recovery for every provider underneath.
3
One data model, always
Your product, HyperSync and your AI coworkers all see the same data model.
Tartan’s Unified API
Built for India’s HRMS and payroll ecosystem, not adapted to it.
100+ systems, from greytHR and Darwinbox to SAP SuccessFactors and Oracle HCM, all behind one contract. Here is exactly what your code sends and receives.
01
One data model
Consistent field names, types and response shape. Whether the employer runs Keka or Workday, your call and your response look identical.
02
Read & write
Read employment and payroll data, and write back deduction instructions, onboarding triggers and roster updates through the same integration.
03
Live event stream
Joiners, exits, promotions and salary revisions are pushed the moment the source record changes, not on your next poll.
04
Custom field access
Surface employer-specific data like grade bands and cost centre codes, or make a passthrough call for raw provider access.
05
Scale-ready infrastructure
Rate limits, pagination, retries and webhook throttling are handled by Tartan, not your engineering team.
Keka{
"emp_code": "K-1042",
"gross_salary": 184000
}Darwinbox{
"employee_id": "DBX-88",
"ctc_breakup": [{ "total_ctc": 184000 }]
}{ "id": "EMP-1042", "payroll": { "gross": 184000, "currency": "INR" } }How a connection works
Live in four steps, with no employer IT team involved.
Tartan Connect sits inside your product, white-labelled. The employer does the connecting. You get the data.
1
Employer selects their HRMS
Through Tartan Connect, embedded and white-labelled in your product flow.
2
Consent is captured
DPDP-compliant, purpose-specific consent before any data access. Logged, revocable, auditable.
3
Tartan normalises
Data is fetched, normalised into the canonical schema and checked for consistency.
4
Data stays live
Updated on schedule, on demand, or pushed by webhook on every employment event.
Acme Finserv · takes about a minute
KekaDarwinboxgreytHRSAP SuccessFactorsZoho PeopleWorkdayThe data model
Four canonical objects. Same structure from every source.
This is what your code works with, whichever HRMS the employer runs.
Employee
Identity, designation, department, date of joining, employment status, reporting structure and contact details.
Payroll
Gross, net, basic, HRA, allowances and deductions like PF and TDS, by salary head and pay period.
Organisation
Company structure, cost centres, business unit hierarchy, headcount bands and employer identity.
Employment Events
Joiner, exit, promotion, salary revision and transfer, typed, timestamped and pushed as they occur.
{
"id": "EMP-1042",
"name": "Priya Menon",
"designation": "Credit Manager",
"department": "Retail Credit",
"date_of_joining": "2021-04-12",
"employment_status": "active",
"manager_id": "EMP-0311",
"work_email": "priya.menon@acmefinserv.in",
"organisation_id": "ORG-ACME"
}Every connector built, maintained, and monitored by TartanHQ. When a vendor updates their API, we update the connector.
For developers
From sandbox to production without a single connector to maintain.
Everything your team needs to build, ship and run the integration, in the order you’ll need it.
DAY 1
Sandbox
Build against synthetic or live HRMS demo data before connecting a single employer. No production credentials needed.
DAY 1
REST API
One consistent schema across all providers. Strongly typed fields. Predictable error handling.
DAY 2
Webhooks
Employment events pushed to your endpoint as they occur. No polling.
DAY 2
Sync controls
Real-time, on-demand or scheduled, configurable per connection.
BEFORE GO-LIVE
Access scoping
Field-level and employee-subset controls. Pull only what your product needs.
EVERY DAY AFTER
Dashboard
Connection status, sync logs, webhook configuration and employer management in one place.
ISO 27001
ISO 27701
AICPA
AWS
Stop building connectors. Start shipping product.
One integration with Tartan connects your product, and your AI coworkers, to every HRMS your customers’ employers run.
