Build on Tarleaks ERP
What the screens can do, the API can do, and what the API can do, your AI tools can do over MCP.
The surface
- A REST API for every app. Each app serves its capabilities as JSON under
/api/<module>/…, with the same licence, permission and company-isolation checks as the screens. - An MCP endpoint for every app. Each of the 36 business apps also serves the Model Context Protocol at
/api/<module>/mcp, plus one gateway for all of them, so Claude, IDEs and agent frameworks can read and act on your data with a permission check on every tool. More than 3,000+ tools come from one catalogue. Connect Claude with a token today; sign-in connection is coming. - API tokens. Server-to-server access with scoped tokens; every call is attributed and audited. Scopes are enforced on MCP; enforcement on the REST API is rolling out.
- Events. Business events (a hire, a payroll run posted, a certificate issued, a ticket, a campaign result) flow over a message bus, so integrations react instead of polling.
- Field-level history. Tracked records keep old and new values for each change, so an integration is easy to debug.
Documentation
The full API reference ships inside the product for each app, generated from the same catalogue the Copilot uses and filtered to the apps in your plan. Start with the API integration guide.
Connecting equipment
- Clock-in machines. Connect ZKTeco, eSSL and Hikvision fingerprint and face machines by typing an address into their menu, any other machine through the on-site bridge (a download on that page), or your own software through the punch API — with a key per machine, examples in five languages and log-file imports.