Everee vs Finch

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.

Finch

Graded on the REST API. An employer grants each connection named product permissions, and limits, error codes and a 99.9 per cent uptime SLA are published. Finch reads payroll and writes deductions but cannot run a payroll. Access tokens never expire, no idempotency keys were found, and writes and most providers need a sales-led plan.

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.

Finch

1. Send Finch-API-Version: 2020-09-17 and Authorization: Bearer <access_token> on every request. A request without the version header fails with 400
2. Call GET /introspect first to see the connection's products, status and whether it is automated or assisted before choosing endpoints
3. Treat a 202 response as data not ready, not as data. Retry with backoff, and expect up to 14 days for an assisted connection's first sync
4. Stay under 20 requests a minute on organisation endpoints and 12 on pay endpoints across all tokens. Batch IDs, and on 429 wait 60 seconds
5. After a deduction write, poll the job by job_id until it completes before enrolling individuals. Enrolment overwrites an existing enrolment
6. Start the MCP server with --code-allow-http-gets or a token without the benefits product when only reads are intended