Skip to main content
Finch supports three environments — Sandbox, Development, and Production — each with different connection limits, provider support, and capabilities. Use the comparison table and environment descriptions below to choose the right one for each stage of testing. Each environment uses separate credentials. In the Finch Dashboard, select your environment from the dropdown and copy the client_id from the Credentials tab before launching Finch Connect.

​
Sandbox, Development, and Production compared

FeaturesFinch SandboxProvider SandboxDevelopmentProduction
AvailabilityAll plansAll plansPro and Premier, upon requestAll plans
Allowed connections10055 *Unlimited
Connect to real providers—✓✓✓
Scheduled data syncs— (?)✓✓✓
Assisted integrations✓——✓
Webhooks✓✓✓✓
*Work with your implementation engineer to discuss more than 5 Development connections.

​
Sandbox environment

You don’t need to test against every provider in Finch’s network. Finch normalizes data across all providers into a consistent schema — your application code does not change based on which provider an employer uses. Use the Field Support matrix to identify which fields are supported for the providers most relevant to your use case.
Finch Sandbox (sandbox=finch) — fully mock data generated and managed by Finch:
  • Create and configure connections programmatically using sandbox-only API endpoints — there is no backing provider system; all data is managed through the Finch API
  • Tests the full authorization flow
  • Supports automated and assisted integrations
Provider Sandboxes (sandbox=provider) — connects to a real provider’s demo or trial account. Recommended for end-to-end testing of automated integrations. Available for a limited number of providers. Data changes are made by logging into the provider’s demo account directly.
A Sandbox application is required to initiate sandbox connections. A free sandbox environment is included with every Finch Developer Dashboard account. If someone on your team has already created one, ask them to add you. If your organization does not have one, sign up or reach out to us.

​
Development environment

Development is a production-like environment for testing with live data, available to Pro and Premier plan customers upon request. Contact your implementation engineer or email implementation-team@tryfinch.com to request access. Before connecting live customer accounts in Development:
  • Development connections cannot be migrated to Production — customers must reauthenticate using your Production client_id.
  • Finch UUIDs are not shared across environments. A Production connection will have entirely new IDs.
  • Gusto and all assisted providers are not supported in Development.
  • Some providers may charge for additional seats created during testing.

​
Production environment

Sandbox and Development connections cannot be used in Production — each environment requires its own credentials and a separate authorization flow. Development connections cannot be migrated to Production; customers must reauthenticate using your Production client_id.
  • Make your first Production connections with friendly customers to complete final validation with real data.
  • Demo or trial provider accounts may successfully connect in Production. All Production connections are billable regardless of account type.
  • Use the disconnect endpoint to disconnect any test, duplicate, or unused connections promptly.
  • Set both client_id and client_secret to your Production values from the Finch Dashboard. Connections cannot move between environments — each requires its own credentials and a new authorization flow.

​
Postman collection

The Finch API Postman collection includes pre-configured requests for all endpoints across Organization, Payroll, Deductions, Documents, and Management. Use environment variables to switch between sandbox and production without reconfiguring requests.

Postman Collection