2024 is the year of the connector - vote here

Query the Employment Hero Payroll (Keypay) API using regular SQL

You're a developer. You're perfectly capable of connecting to the Employment Hero Payroll (Keypay) API and pulling down data. But why waste your time building an API integration when your skills and time are better spent elsewhere?

API integrations are hard to build and maintain. But with SyncHub, you can query your data source using a language you know and love - SQL.

Explore the Employment Hero Payroll (Keypay) Data Model Get started with a free trial

How it works

Get your Employment Hero Payroll (Keypay) data into your favourite reporting tool in just two minutes and three easy steps.

1 2 3 Connect Employment Hero Payroll (Keypay) to SyncHub

Securely connect your cloud software to SyncHub and we'll do the rest.

1 2 3 We sync your data automatically

SyncHub incrementally syncs your data and stages it in a managed data warehouse (yours, or we'll provide one for free). We check for changes so you don't have to.

1 2 3 Build your customized reports

Query and share your data using our built-in Insights platform, or use your own reporting tools like Excel, Tableau or Power BI.

No ODBC driver required

SyncHub runs in the cloud, 24×7. There are no ODBC drivers to install or maintain, and no local computer required to cache your results. Just securely connect SyncHub to your Employment Hero Payroll (Keypay) account and you can be querying your data in just a couple of minutes.

BYOD

Want more power? How about views, stored procedures or triggers? No problem - SyncHub's Bring Your Own Database feature gives you complete control over your database.

Real-time data*

Make a change in Employment Hero Payroll (Keypay) and query it via SQL within minutes. Our feed is so quick, you'll think you're querying Employment Hero Payroll (Keypay) directly!

Your data is secure

Your Employment Hero Payroll (Keypay) data is stored using best-practice security protocols. But if you're still concerned, no worries - just use our BYOD (Bring Your Own Database) option when setting up your account.

Frequently asked questions

Not directly, no. But SyncHub's ERD model, combined with the real-time* sync from Employment Hero Payroll (Keypay), means that it is essentially the same as querying directly.
No. Our solution is cloud-hosted, meaning no installs are required on your own computers. Furthermore, because it is cloud-hosted, SyncHub runs in the background 24-7, keeping your data up to date while you sleep.
If your SQL skills are a little rusty, we've got you covered too. Our AI-powered Query Assistant uses knowledge of your Employment Hero Payroll (Keypay) data model to create SQL queries for you - just describe your problem and watch the magic happen.
SyncHub can poll Employment Hero Payroll (Keypay) as frequently as every five minutes, however this capability may be limited by the amount of data you have and/or the type of plan you have with Employment Hero Payroll (Keypay). The best way to find out is to simply grab a free trial of SyncHub, connect Employment Hero Payroll (Keypay), then see for yourself.
No. SyncHub is a reporting tool and cannot reflect changes back to your cloud application.
We currently sync Account setting, Deduction category, Employee, Employee expense category, Employee leave allowance, Employer liability category, Invoice, Journal account, Leave category, Leave request, Location, Pay category, Employee pay rate, Pay run, Employee pay run, Pay run payslip, Qualification, Role, Roster shift, Timesheet, Work type, Account setting category, Employee location, Invoice line, Payslip bank payment, Payslip earnings line, Payslip accrued leave, Payslip total accrued leave, Payslip leave taken, Payslip deduction, Payslip YTD detail, Payslip employee expense, Payslip kiwi saver payment, Payslip PAYE adjustment, Payslip super adjustment, Payslip super payment, Payslip PAYG adjustment, Roster shift break, Roster shift qualification, Timesheet break and Timesheet dimension (see our Data Model for full details). If there's something else you need just ask.
Your Employment Hero Payroll (Keypay) data is stored in its own dedicated data warehouse, hosted in our Microsoft Azure Sydney Data Center. If you'd like it stored somewhere else (even your own servers), just enquire about our BYOD (bring-your-own-database) option.
Absolutely. Every customer gets their very own isolated data warehouse. Database credentials are salt-encrypted...multi-factor authentication can be activated for your account...we take security very seriously. You can read more about our security best practices here.

Example queries

Check out these example queries for some inspiration

  • select td.ReportingDimensionID, td.TimesheetID, t.WorkTypeID, t.SubmittedByUser from [employmentheropayroll].TimesheetDimension td left join [employmentheropayroll].Timesheet t on td.TimesheetRemoteID = t.RemoteID
  • select tb.StartTime, tb.IsPaidBreak, t.WorkTypeID, t.SubmittedByUser from [employmentheropayroll].TimesheetBreak tb left join [employmentheropayroll].Timesheet t on tb.TimesheetRemoteID = t.RemoteID
  • select rsq.OpportunityID, rsq.RosterID, rs.RoleID, rs.PendingSwapID from [employmentheropayroll].RosterShiftQualification rsq left join [employmentheropayroll].RosterShift rs on rsq.RosterShiftRemoteID = rs.RemoteID
  • select top 32 SuperannuationLiabilityAccountID, SuperannuationExpenseAccountID, PaymentAccountID, PaygLiabilityAccountID, PaygExpenseAccountID, EmployerLiabilityLiabilityAccountID from [employmentheropayroll].AccountSetting order by SuperannuationLiabilityAccountID
  • select top 9 TaxExempt, Source, SgcCalculationImpact, PaymentSummaryClassification, LiabilityGeneralLedgerMappingCode, IsSystem from [employmentheropayroll].DeductionCategory order by TaxExempt
  • select top 9 WorkTypes, WorkPhone, Title, TerminationReason, TaxCodeDeclarationTaxCode, TaxCodeDeclarationStudentLoanRateEndDate from [employmentheropayroll].Employee order by WorkTypes
* Realtime

SyncHub's engine polls for changes every 5 minutes. However, different APIs, and different endpoints within those APIs, may impose restrictions beyond our control - thereby reducing the fidelity of your real-time feed.