Everee vs PayFit

Everee

Everee's API tokens are created in the admin portal of each company instance, and payments wait for a payroll admin's approval unless auto-approval is arranged. The API has no preview or approval endpoint, no single OpenAPI file, no SDK and no changelog, and a company instance starts with a sales call.

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.

Everee

1. Send two headers on every call, authorization: basic <token> and x-everee-tenant-id. Base64-encode a token that starts with sk_ first.
2. Derive each payable's externalId from stable data, never a timestamp or UUID, so a retried create is rejected instead of paying twice.
3. For contractors, call POST /integration/v1/payables/payment-request after all payable items are sent and before admins approve. Without it contractors aren't paid.
4. Send hourly wages through the Timesheets API, not Payables, and assign workLocationId so tax is worked out for the right jurisdiction.
5. Don't expect the API to move money alone. Tell the user a payroll admin must approve in the portal unless auto-approval is enabled, and read Everee's terms on automated access first.

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