Finch unified API profile
Unified API focused on employment systems, including HRIS, payroll, deductions, benefits, and documents.
Research note: This neutral profile summarizes first-party material published by Finch. It was last checked . Capabilities can differ by connector, so verify the exact model, field, action, and refresh behavior required by your product.
Finch at a glance
- Focus
- Employment-system connectivity with broad HRIS and payroll coverage.
- Good fit for
- Benefits, retirement, insurance, fintech, and HR products that need standardized employer, employee, payroll, or deduction data.
- Categories
- HRIS, Payroll, Deductions, Benefits, Documents
- Data delivery
- A synchronized data model: automated integrations refresh on a daily cadence, while assisted integrations have a slower documented cadence.
- Extension path
- Custom fields and Request Forwarding provide access beyond the standardized employment models.
What is Finch?
Finch is a unified API built specifically for the employment ecosystem. It connects employer HRIS and payroll systems to a standardized model covering organization, payroll, deductions, benefits, and employee documents.
- Organization endpoints cover company, directory, individual, and employment data.
- Payroll endpoints expose company pay runs and employee pay-statement details such as earnings, taxes, deductions, and contributions.
- The Deductions API supports reading and managing payroll deductions and contributions, while Documents is documented as a beta product beginning with structured W-4 data.
How do employers connect?
Finch Connect is the employer-facing authorization flow. A product creates a Connect session, the employer selects and authorizes its provider, and the backend exchanges the resulting authorization code for an access token tied to that connection.
- Finch documents automated and assisted integration types, reflecting that not every employment system exposes the same API or authentication path.
- Access tokens represent an employer connection and should be stored on the application backend rather than in durable browser state.
- Products can control which providers and authentication methods appear during onboarding and should review provider-specific setup requirements.
How does Finch synchronize data?
Finch serves employment data from the most recent successful synchronization. Automated integrations are documented with a 24-hour cadence, while assisted integrations refresh every seven days; the API website also describes on-demand refresh support.
- The two integration types trade freshness for provider coverage and should be evaluated separately.
- Webhooks notify an application when data or connection state changes, and the Finch Dashboard provides connection status and API logs.
- Field support, refresh speed, products, and authentication method vary by provider and are published in Finch’s provider network and field-support tools.
How can a product access non-standard data?
Finch exposes custom fields for supplementary employee attributes and Request Forwarding for raw requests to supported provider APIs. Request Forwarding reuses the Finch connection but bypasses Finch’s transformation layer.
- The forwarded request and response remain provider-specific, so the application owns parsing and compatibility for that path.
- Request Forwarding can support reads or writes outside Finch’s standard model when the underlying integration and authentication method support them.
- Availability is limited to documented providers and commercial access conditions, so it should not be assumed across the full network.
What developer tooling is available?
Finch documents SDKs across frontend and backend languages, multiple test environments, provider sandboxes, configurable mock data, a dashboard for connection operations, and an MCP server for agent-oriented workflows.
- Published SDK coverage includes JavaScript, React, Node, Python, Java, Kotlin, Go, and Ruby.
- The sandbox can simulate automated and assisted integrations, while provider sandboxes test against demo or trial accounts where available.
- Finch’s MCP material positions its employment API as a permissioned tool layer for agents that need to read or act on HR and payroll data.
What should buyers verify?
- Finch is employment-focused rather than a general SaaS integration platform; it does not position its core unified API around CRM, accounting, or ticketing categories.
- Automated and assisted integrations have materially different refresh cadences and setup characteristics.
- Products, fields, authentication methods, and write support must be checked for each provider rather than inferred from the overall network.
For a cross-vendor evaluation framework, read the verified unified API buyer’s guide.
Frequently asked questions about Finch
What is Finch best suited for?
Finch is best aligned with products that need HRIS, payroll, deduction, benefits, or employment-document data rather than broad horizontal SaaS connectivity.
Does Finch support payroll writes?
Finch documents write workflows through its Deductions product and some provider-specific Request Forwarding paths. Exact write coverage must be verified per provider.
How often does Finch refresh data?
Finch documents daily refreshes for automated integrations and seven-day refreshes for assisted integrations, with on-demand refresh capabilities also described on its API site.
What is an assisted Finch integration?
An assisted integration uses Finch operations to extend coverage to providers that are not available through a fully automated connection, with a slower refresh cadence than automated integrations.
Sources checked
- Finch unified API overview — official website, checked
- What is Finch? — documentation, checked
- Finch documentation index for agents — documentation, checked
- Finch unified employment API glossary — documentation, checked
- Finch integration types — documentation, checked
- Finch Request Forwarding — documentation, checked
- Finch unified HRIS and payroll API comparison — blog, checked
- Finch MCP server introduction — blog, checked