GoCo API
GoCo publishes a REST API at developers.goco.io spanning companies, employees, payroll, time off, documents, and workflows. Credentials are self-issued from the Marketplace by Full Access Admins, with Bearer token auth. Merge, Finch, and Unified.to also cover it as a unified HRIS connector.
Frequently asked questions
GoCo scores A on the API Report Card. GoCo publishes a REST API at developers.goco.io spanning companies, employees, payroll, time off, documents, and workflows. Credentials are self-issued from the Marketplace by Full Access Admins, with Bearer token auth. Merge, Finch, and Unified.to also cover it as a unified HRIS connector.
GoCo has a workable official integration path. Most engineering teams can build against it directly. Open API: self-serve, documented, with SDKs
GoCo is a cloud-native, all-in-one HRIS for U.S. small and mid-sized businesses.
Vertical: Enterprise / HR / ERP, specifically an SMB HRIS + benefits admin + workflow-automation platform serving U.S. companies roughly 10–500 employees. HR admins onboarding new hires (offer letters, I-9, W-4, direct deposit, document e-sign) via configurable workflows. Employees self-serving pay stubs, W-2s, PTO balances, benefits enrollment, and personal data updates.
Medium within the U.S. SMB HRIS segment. GoCo is consistently listed among BambooHR alternatives on G2/Capterra/GetApp and is a recognized name among benefits brokers, but customer count is materially smaller than category leaders (BambooHR, Gusto, Rippling, Paylocity, ADP RUN).
Founded: 2015 (Houston, TX).. Founders: Nir Leibovich (CEO), Michael Gugel (CTO), Jason Wang.. HQ: Houston, Texas, USA.. Ownership: Acquired by Intuit (announced 2025); operates as an Intuit subsidiary alongside QuickBooks Workforce and Intuit Enterprise Suite.
Founded 2015 (~11 years old as of 2026). Cloud-native SaaS from day one, no on-prem legacy. Modern responsive web app and mobile clients, SSO support, configurable workflow engine, and an OpenAPI-spec public REST API.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.