PayFit vs Worklio

PayFit

A public OpenAPI 3.0 file, llms.txt and scoped keys let a paying customer's agent read payroll outputs and write absences. The API cannot run or approve a payroll, new partner integrations are not being accepted, and no idempotency keys or SDKs were found.

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.

PayFit

1. Have a company admin create the key at app.payfit.com/integrations/hub/api with only the scopes the task needs. The key is shown once
2. POST the key to https://oauth.payfit.com/introspect to get company_id, then call https://partner-api.payfit.com/companies/{companyId}/...
3. Page lists with nextPageToken and maxResults, which defaults to 10 and stops at 50
4. Check before repeating a failed POST. There is no idempotency key, and POST /absences creates an absence that is already validated
5. A collaborator or contract created through the API stays incomplete until an HR admin finishes it in the PayFit app, and a new contract takes 2 to 5 minutes to appear

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