Employment Hero Payroll vs Worklio

Employment Hero Payroll

Five public Swagger 2.0 files describe 660 to 821 operations per region, and any payroll user can generate an API key without a partner review. The key carries its user's whole access, no idempotency keys or API changelog were found, and the only official client is for .NET.

Worklio

Worklio documents 853 REST operations with an OpenAPI fragment on every reference page, and a developer can register for the sandbox without a sales call. No rate limits or public SDK were found, the status page is password protected, and the payroll guide tells callers to treat an HTTP 500 as the signal to finalise.

Employment Hero Payroll

1. Send the API key as the Basic auth username with a blank password, for example curl -u {api_key}: https://api.yourpayroll.com.au/api/v2/user
2. Pick the Swagger file for the business's region (swagger-au.json, swagger-nz.json, swagger-uk.json, swagger-sg.json, swagger-my.json). Paths and models differ by region
3. Stay under 5 requests a second per key and IP address. A 429 answered our test with retry-after: 1
4. Page lists with $skip and $top (100 at most). Filter property names are capitalised, unlike the camelCase JSON
5. Read GET /api/v2/business/{businessId}/payrun/{payRunId}/warnings before POST .../finalise. Finalise can lodge with the tax office and publish pay slips in the same call

Worklio

1. Send api-version: 2.0 on /wep calls. The reference marks the header as required
2. Get a token from POST https://api.worklio.com/connect/token with the password grant and scope api. It lasts 24 hours, so fetch a new one daily
3. Run payroll as start, next until it answers 500 with "Next step operation is not allowed", then finalize. Don't treat that 500 as a failure
4. Don't retry bonus, off-cycle, void or termination payroll starts blindly. The reference says those calls are not idempotent
5. Most /wep list endpoints return the whole result set. Paging, filter and sort work only under /api/public, and a DataToken expires after 60 seconds