Hamara HR 数据 API:打卡、工资单与 KYC
Hamara HR(Google Play 上亦作 Hamara Jobs / Qjobs)是 Quess Corp 面向 Heptagon PeopleDesk 栈上员工的自助应用。选定公司租户后,员工用邮箱和密码登录(部分租户提供 Truecaller OTP),首页打开 GPS 考勤打卡、月度工资单、请假申请与跟踪、Aadhaar 与银行 KYC、费用报销、数字工牌,以及团队主管查看下属详情与经理自助。Quess Corp 总部位于班加罗尔,是印度的人力派遣与劳动力管理公司;该应用是 Quess 员工及其他 PeopleDesk 租户在印度使用的白标手机端,与 Darwinbox、greytHR、ADP Mobile 同台,服务派遣垂直的员工自助。支持邮箱为 [email protected]。
工资单月份列表把每位员工的 dateOfJoin 钉在 defaultYear 上,再给出按 payslipType、filename 与 url 索引的可下载 monthList(激励与报销类型并列)。GPS 打卡以 checkInTime / checkOutTime 落在 shiftDate 上,关联 shiftName、outletId 与 attendance_type,之前还有一次可设置 block_checkin 的预检。请假行带 fromDate、toDate、noOfDays、leaveTypeName 与 approvalFlag。
身份与发薪账户字段挨着这份工时记录。KYC 行返回 labelName / value,附 qcStatus 与 isVerified;银行核验补上 aadhaarNumber、validAadhaar、faceScore、upiId 以及 IFSC 目录形态(IFSC、BANK、BRANCH、MICR)。费用报销列出 claimNo、claimAmount、billNo 与 cityName。数字工牌暴露 employeeId、designation 与 validUpto;主管查询再加下属的 contactNo、pincode、latitude 与 longitude。会话引导挂在租户选择返回的 subDomainName、customerId 之后的 token、companyCode 与 companyUrl 上。
薪酬、入职与外勤系统都需要这份按员工划分的记录。财务把 payslipType 与当月 PDF url 和按日 checkInTime 关联,在发单前抓住漏打卡。入职工具在首次发薪前确认 aadhaarNumber 与 IFSC / upiId 账户。差旅费用机器人把 claimAmount 与当日 outletId 对账。外勤把下属 latitude / longitude 打点,再叠请假 approvalFlag。openData Studio 将这份考勤、工资单、KYC 与报销记录转化为可调用的开放数据,支撑上述集成。
应用截图
API 端点一览
以下端点与请求/响应示例均依据应用界面推导重构,为示意说明,并非实际抓包。
列出租户域名
POST
/v1/tenants/resolveopendata按员工邮箱返回匹配的 PeopleDesk 租户,供应用在登录前设置运行时公司主机。
认证方式: 未鉴权的租户选择。JSON 体携带员工邮箱,供应用在登录前列出匹配的公司租户。
- company
- subDomainName
- customerId
- quessCompany
- quessCompanyFlag
- quessLabel
- mobileLogin
- companyHelpline
- companyHelplineEmail
- privacyPolicyLink
- termsAndConditionLink
- isFindEnable
- isDropdownFlag
- userLoginDisableFlag
POST /v1/tenants/resolve HTTP/1.1 Content-Type: application/json { "email": "[email protected]", "platform": "Android" }{ "status": true, "message": "ok", "domains": [ { "company": "Quess Corp", "subDomainName": "quess", "customerId": 23, "quessCompany": 1, "quessCompanyFlag": 1, "quessLabel": "Hamara HR", "mobileLogin": 1, "companyHelpline": "1800-000-000", "companyHelplineEmail": "[email protected]", "privacyPolicyLink": "https://example.invalid/privacy", "termsAndConditionLink": "https://example.invalid/terms", "isFindEnable": 0, "isDropdownFlag": 1, "userLoginDisableFlag": 0 } ] }员工登录
POST
/v1/identity/sessionosint验证员工身份,返回会话 token 以及公司、自助服务 URL、地理与 MFA 开关,用于个性化首页。
认证方式: 邮箱 + 密码(租户已解析时可选 customerId)。无需事先 Bearer。响应 token 在后续调用中作为 Authorization Bearer 发送。
- token
- userId
- loginUserId
- loggedUserId
- companyCode
- companyName
- companyUrl
- customerName
- employeeMobileNumber
- logo
- profilePicture
- mssUrl
- attendanceMssUrl
- shiftRosterMssUrl
- otpFlag
- mfaLoginFlag
- timeZone
- supportEmailId
- trueCallerFlag
- mobileVerifyFlag
- geoLocation
- beatFlag
- gpsGlag
POST /v1/identity/session HTTP/1.1 Content-Type: application/json { "email": "[email protected]", "password": "******", "customerId": 23, "platform": "Android" }{ "status": true, "message": "Login successful", "token": "<session_token>", "userId": "U-10432", "loginUserId": "[email protected]", "loggedUserId": 10432, "companyCode": "QUESS", "companyName": "Quess Corp", "companyUrl": "https://tenant.example.invalid/", "customerName": "Quess Corp", "employeeMobileNumber": "9876543210", "logo": "https://cdn.example.invalid/logo.png", "profilePicture": "https://cdn.example.invalid/profile.png", "mssUrl": "https://mss.example.invalid/", "attendanceMssUrl": "https://mss.example.invalid/attendance", "shiftRosterMssUrl": "https://mss.example.invalid/roster", "otpFlag": 0, "mfaLoginFlag": 0, "timeZone": "Asia/Kolkata", "supportEmailId": "[email protected]", "trueCallerFlag": 1, "mobileVerifyFlag": 1, "geoLocation": [{"latitude": "12.9716", "longitude": "77.5946"}], "beatFlag": 0, "gpsGlag": "1" }首页仪表盘(主)
POST
/v1/home/overviewopendata加载已登录员工的首页信封——身份、入职日期、币种、数字工牌与人脸检测开关,以及仪表盘磁贴背后的考勤/请假自助 URL。
认证方式: 使用员工登录返回的 Bearer 会话 token。
- employeeId
- employeeName
- employee_ref_id
- companyCode
- companyName
- companyUrl
- customerName
- dateOfBirth
- dateOfJoin
- currency
- attendanceMessage
- digitalIdCard
- faceDetectionFlag
- locationTracking
- blockCheckin
- leaveMssUrl
- attendanceMssUrl
POST /v1/home/overview HTTP/1.1 Authorization: Bearer <session_token> Content-Type: application/json { "platform": "Android" }{ "status": true, "employeeId": "E-10432", "employeeName": "Priya Sharma", "employee_ref_id": "QC10432", "companyCode": "QUESS", "companyName": "Quess Corp", "companyUrl": "https://tenant.example.invalid/", "customerName": "Quess Corp", "dateOfBirth": "1994-03-12", "dateOfJoin": "2021-06-01", "currency": "INR", "attendanceMessage": "Shift starts at 09:00", "digitalIdCard": 1, "faceDetectionFlag": 1, "locationTracking": 1, "blockCheckin": 0, "leaveMssUrl": "https://mss.example.invalid/leave", "attendanceMssUrl": "https://mss.example.invalid/attendance" }打卡预检
POST
/v1/time/punch-gateopendata控制打卡按钮:返回是否拦截签到、上一次考勤动作,以及员工提交 GPS 打卡前的提示。
认证方式: 使用员工登录返回的 Bearer 会话 token。
- block_checkin
- previous_Action
- prompt_message
- status
POST /v1/time/punch-gate HTTP/1.1 Authorization: Bearer <session_token> Content-Type: application/json { "employeeId": "E-10432", "latitude": "12.9716", "longitude": "77.5946" }{ "status": true, "block_checkin": 0, "previous_Action": "checkout", "prompt_message": "You can check in now" }GPS 考勤打卡(签到)
POST
/v1/time/clock-inopendata记录员工的 GPS 签到打卡,返回打卡时间 checkInTime、已排班次与网点,供考勤磁贴使用。
认证方式: 使用员工登录返回的 Bearer 会话 token。
- checkInTime
- shiftName
- shiftid
- outletId
- attendance_type
- status
- message
POST /v1/time/clock-in HTTP/1.1 Authorization: Bearer <session_token> Content-Type: application/json { "employeeId": "E-10432", "latitude": "12.9716", "longitude": "77.5946", "outletId": "OUT-12" }{ "status": true, "message": "Checked in", "checkInTime": "09:02:11", "shiftName": "General", "shiftid": 4, "outletId": "OUT-12", "attendance_type": "P" }考勤明细(按日)
POST
/v1/time/day-ledgeropendata拉取员工在日期窗口内的按日打卡、休息、班次与补卡开关——即 You 页考勤日历背后的记录。
认证方式: 使用员工登录返回的 Bearer 会话 token。
- employeeId
- employeeJoinDate
- from
- to
- attendanceType
- fullDayHours
- halfDayHours
- halfDayFlag
- overtimeFlag
- multiShiftFlag
- autoShiftFlag
- regularizeCount
- timesheetFlag
- checkInTime
- checkOutTime
- breakInTime
- breakOutTime
- shiftName
- shiftid
- shiftDate
- outletId
- allowRegularisation
- allowOtRequest
- od_flag
POST /v1/time/day-ledger HTTP/1.1 Authorization: Bearer <session_token> Content-Type: application/json { "employeeId": "E-10432", "from": "2026-09-01", "to": "2026-09-30" }{ "status": true, "employeeId": "E-10432", "employeeJoinDate": "2021-06-01", "from": "2026-09-01", "to": "2026-09-30", "attendanceType": "monthly", "fullDayHours": 8, "halfDayHours": 4, "halfDayFlag": 1, "overtimeFlag": 1, "multiShiftFlag": 0, "autoShiftFlag": 1, "regularizeCount": 2, "timesheetFlag": 1, "attendanceDetails": [ { "shiftDate": "2026-09-12", "checkInTime": "09:02:11", "checkOutTime": "18:11:04", "checkOutFlag": 1, "breakInTime": "13:00:00", "breakOutTime": "13:30:00", "attendance_type": "P", "shiftName": "General", "shiftid": 4, "shiftType": "fixed", "shiftTotalDuration": "09:00", "outletId": "OUT-12", "allowRegularisation": 1, "allowOtRequest": 1, "od_flag": 0 } ] }工资单月份与 PDF
POST
/v1/pay/statementsopenfinance列出员工可下载的工资单月份(及激励/报销类型),并返回 My Documents 工资单页使用的 PDF filename/url。
认证方式: 使用员工登录返回的 Bearer 会话 token。
- dateOfJoin
- defaultYear
- filename
- folderName
- url
- payslipType
- incentiveType
- reimbursementType
- monthList
- display
- month
- year
- signatureFlag
- documentsWithSignature
- widgetTitle
- widgetCategories
- categoryName
- categoryUrl
POST /v1/pay/statements HTTP/1.1 Authorization: Bearer <session_token> Content-Type: application/json { "employeeId": "E-10432", "year": 2026 }{ "status": true, "message": "ok", "dateOfJoin": "2021-06-01", "defaultYear": 2026, "filename": "payslip_Sep_2026.pdf", "folderName": "payslips", "url": "https://cdn.example.invalid/payslips/E-10432/2026-09.pdf", "payslipType": "salary", "incentiveType": "variable", "reimbursementType": "claim", "monthList": [ { "display": "Sep 2026", "month": 9, "year": 2026, "icon": "pdf", "signatureFlag": 1, "documentsWithSignature": 1 } ], "dashData": { "payslipWidget": { "widgetTitle": "Payslips", "widgetIcon": "payslip", "widgetCategories": [ {"categoryName": "Salary", "categoryUrl": "salary"} ] } } }请假列表
POST
/v1/time-off/requestsopendata返回员工请假申请,含类型、天数、半天标记与审批状态——即请假磁贴背后的列表。
认证方式: 使用员工登录返回的 Bearer 会话 token。
- id
- employeeId
- customerId
- fromDate
- toDate
- allDate
- noOfDays
- leaveType
- leaveTypeName
- isHalfDayFlag
- approvalFlag
- reason
- createdAt
- createdBy
- leaveTypeCount
- attendanceStartCycle
- attendanceEndCycle
- halfDayFlag
- leaveBreFlag
- totalCount
POST /v1/time-off/requests HTTP/1.1 Authorization: Bearer <session_token> Content-Type: application/json { "employeeId": "E-10432", "approvalFlag": 0 }{ "status": true, "totalCount": 2, "leaveType": "CL", "leaveTypeCount": 6, "attendanceStartCycle": "2026-09-01", "attendanceEndCycle": "2026-09-30", "halfDayFlag": 1, "leaveBreFlag": 0, "list": [ { "id": 88120, "employeeId": "E-10432", "customerId": 23, "fromDate": "2026-10-05", "toDate": "2026-10-06", "allDate": "2026-10-05,2026-10-06", "noOfDays": 2, "leaveType": "CL", "leaveTypeName": "Casual Leave", "isHalfDayFlag": 0, "approvalFlag": 0, "reason": "Family function", "createdAt": "2026-09-28 11:04:00", "createdBy": "E-10432" } ] }KYC 明细
POST
/v1/identity/kyc-profileosint读取员工 KYC 字段行(Aadhaar 与银行证明),含质检状态、OTP 开关以及用于填写银行信息的 IFSC 辅助 URL。
认证方式: 使用员工登录返回的 Bearer 会话 token。
- qcStatus
- otpFlag
- otpNote
- pendingRequestFlag
- pendingRequestNote
- id
- labelName
- value
- isVerified
- isEdit
- bankVerifyUrl
- bankVerifyToken
- bankGetOtherDetailsUrl
POST /v1/identity/kyc-profile HTTP/1.1 Authorization: Bearer <session_token> Content-Type: application/json { "employeeId": "E-10432" }{ "status": true, "qcStatus": "pending", "otpFlag": 1, "otpNote": "OTP sent to registered mobile", "pendingRequestFlag": 1, "pendingRequestNote": "Bank proof under review", "response": [ { "id": 1, "labelName": "Aadhaar", "value": "XXXX-XXXX-3210", "isVerified": 0, "isEdit": 1, "otpFlag": 1, "bankDetails": { "bankVerifyUrl": "https://ifsc.example.invalid/", "bankVerifyToken": "<bank_verify_token>", "bankGetOtherDetailsUrl": "https://ifsc.example.invalid/SBIN0001234" } } ] }银行 / Aadhaar 核验
POST
/v1/identity/account-checkopenfinance核验员工 Aadhaar 与银行账户,返回人口学字段、人脸匹配分、UPI id 以及 IFSC 目录记录(BANK、BRANCH、MICR、IMPS/NEFT/RTGS/UPI)。
认证方式: 使用员工登录返回的 Bearer 会话 token。
- aadhaarNumber
- validAadhaar
- fullName
- fatherName
- dob
- gender
- faceScore
- faceStatus
- accountExists
- upiId
- zip
- careOf
- otpSent
- IFSC
- BANK
- BANKCODE
- BRANCH
- ADDRESS
- CITY
- STATE
- DISTRICT
- MICR
- IMPS
- NEFT
- RTGS
- UPI
POST /v1/identity/account-check HTTP/1.1 Authorization: Bearer <session_token> Content-Type: application/json { "employeeId": "E-10432", "aadhaarNumber": "XXXXXXXX3210", "ifsc": "SBIN0001234" }{ "status": true, "data": { "aadhaarNumber": "XXXXXXXX3210", "validAadhaar": true, "fullName": "Priya Sharma", "fatherName": "Ramesh Sharma", "dob": "1994-03-12", "gender": "F", "faceScore": 92, "faceStatus": true, "accountExists": true, "upiId": "priya@sbi", "zip": "560001", "careOf": "Ramesh Sharma", "otpSent": true, "kycBankDetailsResult": { "IFSC": "SBIN0001234", "BANK": "State Bank of India", "BANKCODE": "SBIN", "BRANCH": "MG Road", "ADDRESS": "MG Road, Bengaluru", "CITY": "Bengaluru", "STATE": "Karnataka", "DISTRICT": "Bengaluru Urban", "CENTRE": "Bengaluru", "CONTACT": "08012345678", "MICR": "560002002", "IMPS": true, "NEFT": true, "RTGS": true, "UPI": true } } }费用报销列表
POST
/v1/expense/claimsopenfinance列出员工费用报销,含单号、金额、类别、票据与审批标记——即报销磁贴背后的台账。
认证方式: 使用员工登录返回的 Bearer 会话 token。
- id
- claimNo
- claimAmount
- totalAmount
- categoryName
- subCategoryName
- categoryId
- subCategoryId
- billNo
- claimReason
- status
- approvalFlag
- employeeId
- employeeName
- fromDate
- toDate
- cityName
- expenseId
- expenseName
- activityDate
- branchId
POST /v1/expense/claims HTTP/1.1 Authorization: Bearer <session_token> Content-Type: application/json { "employeeId": "E-10432" }{ "status": true, "claims": [ { "id": 4401, "claimNo": "CLM-4401", "claimAmount": 1850.5, "totalAmount": 1850.5, "categoryName": "Travel", "subCategoryName": "Local conveyance", "categoryId": 2, "subCategoryId": 9, "billNo": "B-7781", "claimReason": "Client site commute", "status": "pending", "approvalFlag": 0, "employeeId": "E-10432", "employeeName": "Priya Sharma", "fromDate": "2026-09-10", "toDate": "2026-09-10", "cityName": "Bengaluru", "expenseId": 12, "expenseName": "Auto", "activityDate": "2026-09-10", "branchId": 7 } ] }数字工牌
POST
/v1/badge/currentosint返回员工数字工牌——工号、姓名、职务、照片与有效期——对应首页数字工牌磁贴。
认证方式: 使用员工登录返回的 Bearer 会话 token。
- employeeId
- employeeName
- designation
- profilePicture
- validUpto
- companyLogo
- generateFlag
POST /v1/badge/current HTTP/1.1 Authorization: Bearer <session_token> Content-Type: application/json { "employeeId": "E-10432" }{ "status": true, "companyLogo": "https://cdn.example.invalid/logo.png", "generateFlag": 1, "idCard": { "employeeId": "E-10432", "employeeName": "Priya Sharma", "designation": "Associate", "profilePicture": "https://cdn.example.invalid/profile.png", "validUpto": "2027-03-31" } }团队主管查看员工详情
POST
/v1/team/member-profileosint供团队主管读取下属的联系方式、网点地理(latitude/longitude、pincode)与经理链——即 My Team 员工详情背后的记录。
认证方式: 使用员工登录返回的 Bearer 会话 token(团队主管 / 经理自助会话)。
- empId
- employeeName
- contactNo
- doj
- roleName
- branchName
- branchCode
- branchId
- branchStreet
- buildingName
- cityName
- state
- country
- pincode
- latitude
- longitude
- managerEmpId
- managerId
- managerName
- managerUserId
- segmentName
- profilePicture
POST /v1/team/member-profile HTTP/1.1 Authorization: Bearer <session_token> Content-Type: application/json { "empId": "E-10432" }{ "status": true, "empDetails": { "empId": "E-10432", "employeeName": "Priya Sharma", "contactNo": "9876543210", "doj": "2021-06-01", "roleName": "Associate", "branchName": "Bengaluru MG Road", "branchCode": "BLR-01", "branchId": 7, "branchStreet": "MG Road", "buildingName": "Quess Tower", "cityName": "Bengaluru", "state": "Karnataka", "country": "India", "pincode": "560001", "latitude": "12.9716", "longitude": "77.5946", "managerEmpId": "E-2001", "managerId": 2001, "managerName": "Anita Rao", "managerUserId": "anita.rao", "segmentName": "Staffing", "profilePicture": "https://cdn.example.invalid/profile.png" } }
数据类别
- 租户域名
- 员工资料
- GPS 考勤
- 工资单
- 请假申请
- KYC / Aadhaar
- 银行 IFSC
- 费用报销
- 数字工牌
- 团队名册
数据使用场景与案例
按打卡做薪酬月结
财务把每位员工的 payslipType 与 monthList url 和按日 checkInTime / checkOutTime、fullDayHours 关联,在发出 PDF 前抓住漏打卡。
Aadhaar 与 IFSC 入职校验
劳动力入职工具读取 aadhaarNumber、validAadhaar、faceScore 以及 IFSC / BANK / MICR / upiId 记录,在首次发薪前确认工资账户。
费用报销审计轨迹
差旅费用机器人拉取 claimNo、claimAmount、billNo、cityName 与 approvalFlag,把市内交通报销与同一 activityDate 的考勤 outletId 对账。
主管侧地理名册
外勤看板用团队员工详情中的 latitude / longitude 与 pincode 打点,再叠 GPS 打卡,区分在岗与请假(leaveTypeName、approvalFlag)。
常见问题
Hamara HR 接口暴露哪些数据?
按员工划分的 PeopleDesk 记录:租户选择(subDomainName、customerId、quessLabel),登录会话(token、companyCode、companyUrl),仪表盘身份(employeeId、dateOfJoin、currency),GPS 考勤(checkInTime、outletId、shiftName),工资单月份(payslipType、filename、url),请假(leaveTypeName、noOfDays、approvalFlag),KYC/Aadhaar 与 IFSC 银行字段,费用报销(claimNo、claimAmount),数字工牌,以及主管侧下属地理信息。
应用如何认证其请求?
员工先按工作邮箱解析公司租户,再用邮箱和密码登录(部分租户提供 Truecaller OTP)。该登录返回的会话 token 在后续调用中作为 Authorization Bearer 发送。会话上的 MFA 与手机核验开关告诉首页是否需要第二因素。
哪些调用承载薪酬与 KYC?
工资单月份返回 dateOfJoin、payslipType、filename 以及各月 PDF url。KYC 字段行暴露 labelName、value、qcStatus 与 isVerified;银行/Aadhaar 核验再补上 validAadhaar、faceScore、upiId 以及 IFSC 目录记录(BANK、BRANCH、MICR、UPI)。
每家公司的 API 主机都一样吗?
不一样。每个 PeopleDesk 租户有自己的主机,在租户选择时确定,登录时以 companyUrl 返回,因此不同客户的员工不共用同一个 API 主机。
与 Hamara HR 相似的应用
- Darwinbox — Darwinbox 是印度自研的端到端人力资本管理平台,员工端用于考勤打卡、请假和工资单,面向 Darwinbox 租户。
- greytHR — greytHR 是面向印度企业的人力资源与薪资套件,员工应用可一键办理请假、考勤和工资单。
- ADP Mobile Solutions — ADP Mobile Solutions 是 ADP 的员工自助应用,供在 ADP 发薪的公司查看薪酬、工时并处理人事事务。
- Keka HR — Keka 是总部位于海得拉巴的人力资源与薪资平台,员工可在同一租户上打卡、请假和查看薪酬。
- Zoho People — Zoho People 是 Zoho 的云端人力资源系统,提供请假、考勤签到签退及日常人事自助门户。
- PagarBook — PagarBook 是印度中小企业用的员工考勤与发薪应用,用于打卡、发工资和处理法定缴款。
- Workday — Workday 是企业级人力资本管理套件,移动端可签到签退、查看团队出勤,并处理工时、薪酬和人事事务。
相关主题
- Hamara HR API
- Hamara Jobs Qjobs API
- Quess Corp 员工应用
- PeopleDesk 考勤 API
- 工资单月份 API
- Aadhaar KYC IFSC
- 费用报销列表
- 员工自助 API
需要集成这个 App 的数据 API?
我们可为任意指定 App 交付定制集成——源码交付 USD 500 起,或托管 API 按调用计费。告诉我们您需要的数据即可。
- 每个项目均签 NDA 与 SOW
- 3–7 天交付
- 验收通过后才付款
- 仅在授权范围内作业