Auris Payroll API

Does Auris Payroll have a public API?

Auris Payroll, the platform formerly sold as Heartland Payroll with its client login at heartlandpayroll.com, does not publish a self-serve developer API for reading payroll history and quarterly reports. Its integrations run through partner connectors to accounting, benefits and retirement systems. Integuru's 6 verified actions give your own Auris login direct HTTP access to the client list, employee census, payroll archive and quarterly reports.

The pattern is the same for any payroll platform whose API is reserved for certified partners. Integuru authenticates with the credentials your team already uses, calls the endpoints the web app itself calls, and keeps the session alive through auth auto-healing, so the integration survives UI redesigns. The ADP integration works the same way for a much larger action surface, and the fintech industry page covers reconciliation across payroll, banking and payments as one pipeline.

What you can do with the Auris Payroll API

Client roster. list_clients returns every client account the login can see. Leave keyword blank for all of them, or search one column with search_column (1 Client ID, 2 Client Legal, 3 Client DBA, 4 Federal ID, 5 Support ID) and a match mode in operator (1 Contains, 2 Equals, 3 Begins With, 4 Ends With). A status of -1 includes every account status. get_client_info takes the client_code from that list and returns the client record.

Employee census. list_employees pages through a client's employees 50 at a time (page, page_size). It defaults to active staff (status 'A'); pass 'T' for terminated employees and pay_type_code to narrow by pay type.

Payroll runs. list_payroll_archive lists a client's completed payroll runs, optionally narrowed to one calendar year.

Quarterly tax reports. list_quarterly_reports lists the quarterly filings for a client, again filterable by year.

Session. get_userprofile returns the profile of the authenticated user, which is how a batch job confirms which account a stored connection is bound to before it fans out.

Every client-scoped action keys on client_code, so a typical pipeline calls list_clients once and then runs the other actions per client.

Who uses this

Fintech teams reconciling payroll liabilities against bank activity pull the payroll archive and quarterly reports per client instead of waiting for PDFs. Accounting and bookkeeping practices that service many employers through one Auris login use list_clients and list_employees to keep their own systems in step with the census. Workforce tools that already read scheduling data from Homebase or Workeasy through Integuru add Auris for the payroll side under the same auth model. Teams weighing routes for other payroll systems can read the platform API guides for Gusto, Paychex and Rippling.

Setup notes

Integuru authenticates against www.heartlandpayroll.com with your Auris Payroll user, including any 2FA the account requires, and refreshes the session automatically. Start with list_clients, which needs no parameters, to collect client codes; every other client action requires one. list_employees defaults to active employees, so pass status: 'T' explicitly when year-end work needs terminated staff.

Get started

Install the CLI and connect your Auris Payroll login:

npm install -g integuru

Or sign in at app.integuru.com and add Auris Payroll. To bring payroll submission, employee edits or pay stub retrieval into the same workflow, the Managed Service scopes and builds those actions against your account.