The API isn't an add-on. It's the product.
The dashboard and the mobile app are both clients of the same REST API — which means there is no capability locked inside a screen. Anything an administrator can do, your systems can do too.
Stop exporting spreadsheets into payroll.
The most expensive part of most attendance systems isn't the licence — it's the person who spends the last three days of every month reformatting a CSV so payroll will accept it, and the errors that survive that process.
WMS360 exposes attendance, leave, overtime and approval state over a documented HTTP API. Your payroll run pulls what it needs, when it needs it, from the system of record.
- Documented with OpenAPI — a machine-readable contract, so clients can be generated rather than hand-written against guesswork.
- Token authentication with the same granular permission model the UI uses. An integration account holds exactly the rights it needs.
- Stable public identifiers on every record, safe to store on your side as a foreign key.
# Request
GET /api/v1/reports/attendance?from=2026-08-01&to=2026-08-31
Authorization: Bearer <token>
# Response
{
"periodStatus": "locked",
"employees": [
{
"publicId": "a3f1c8e2-...",
"employeeCode": "EMP-10428",
"presentDays": 24,
"leaveDays": 2,
"overtimeHours": 11.5,
"approvedBy": "sup-4471"
}
]
}
Illustrative shape. The live contract is the OpenAPI document that ships with your deployment.
Where verified attendance usually needs to go.
Payroll
Pull present days, leave, and approved overtime for a locked period. Because the period is locked, the numbers you pull are the numbers that stay.
ERP / HRMS
Keep the employee master in step in whichever direction suits you — WMS360 as the source, or your HRMS as the source with WMS360 consuming it.
BI & reporting
Feed attendance and compliance data into the warehouse you already report from, rather than maintaining a second reporting stack here.
How an integration usually goes.
Create an integration user
With a role holding only the permissions the integration needs — typically read-only reporting rights.
Read the OpenAPI document
Generate a client from the contract in whatever language your payroll or ERP tooling is written in.
Pull after the period locks
Lock the payroll period, then pull. You get a stable dataset instead of a moving one.
Tell us what it has to talk to.
Bring the name of your payroll or ERP system to the demo and we'll walk through exactly which endpoints that integration would use.