Reference · built on requestConnectorHR, scheduling & workforce

Gusto

Employees, jobs and compensations, pay schedules, payrolls, time sheets, and time off from Gusto through its App Integrations API.

Request accessPricing ↗

About

Gusto runs payroll, benefits, and HR for small businesses in the United States. Its App Integrations API exposes companies, employees and their employments, jobs and compensations, departments, locations, pay schedules and pay periods, payrolls, time off policies and requests, and a Time Tracking API that accepts classified hours by shift. Access is by OAuth2 per company, versioned by date, with webhooks for employee, payroll, and pay schedule events.

An operator on Fibric reads the roster, pay periods, and time off, and proposes time sheets or a time off policy assignment for your approval. Each proposal carries its reason and its undo.

This is a reference listing. It documents what Fibric would read from Gusto and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Employees of a company, their employments, terminations, rehires, and employment history
  • Jobs and compensations per employee, including the company's custom fields
  • Pay schedules, pay periods, termination pay periods, and pay schedule assignments
  • Payrolls for a company, with earning types and company notifications
  • Time off policies, employee time off activities, and time off requests for a company
  • Time sheets and payroll syncs under the Time Tracking API
  • Webhook events such as employee.created, employee.terminated, employee.termination_effective, employee.rehired, and payroll and pay schedule events

Proposed actions

  • Target capability: propose a time sheet of classified hours by shift through POST /v1/companies/{uuid}/time_tracking/time_sheets
  • Target capability: propose adding employees to a time off policy
  • Target capability: propose an employee termination or rehire record
  • Target capability: propose a payroll sync of submitted hours

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Hand approved hours to payroll by shift

    Take signed-off shifts from the scheduling system and propose a time sheet per employee and job, with hours already split into regular and overtime.

    With Timesheet Signoff, Overtime Guard

  • Keep the roster and the schedule on the same list

    Sync employees, terminations, and rehires from webhook events and propose the schedule removals or additions that follow.

    With Shift Coverage, Offboarding Sweep

  • Check labor against the pay period

    Read pay periods and submitted time sheets and propose the cutoff reminders and the budget flags before the payroll runs.

    With Labor Budget, Month-End Cutoff

Requirements

  • An app in the Gusto Developer Portal with at least one redirect URI, plus Production Pre-Approval and a Security Review before production credentials are issued
  • A demo company on api.gusto-demo.com for all testing; Gusto issues no production test accounts
  • Scopes assigned during review, named resource:action such as employees:read
  • For time sheets, an application created with Gusto's own time tracking features disabled
Authentication
OAuth2 per company: an app registered in the Gusto Developer Portal exchanges a code for an access_token and refresh_token, the access token expiring after 7200 seconds; organization-level api_tokens come from the same portal.

Limits

  • Gusto does not support a customer connecting its own systems directly to its own Gusto account; the API serves software with shared customers
  • 200 requests per minute per OAuth grant, measured over a 60-second rolling window; excess returns 429
  • Time data must be sent by shift with hours classified as regular, overtime, or double overtime, not aggregated per pay period
  • Only one application per organization may hold a webhook subscription; unacknowledged deliveries retry up to 16 times over 3 days

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Gusto ↗

Questions and answers

Can a company connect its own Gusto account through this API?
Not today. Gusto's documentation states it does not support API access for customers connecting their own systems directly to their Gusto account. The App Integrations API serves software products that share customers with Gusto, after Production Pre-Approval and a Security Review.
How is time sent to Gusto?
Through the Time Tracking API, one time sheet per shift with entries classified by pay classification such as Regular, overtime, and double overtime. Hours then appear under Time & Attendance and are synced to payroll from the Time Tracking page or the run payroll flow.
How are API versions managed?
By date. Requests carry an X-Gusto-API-Version header such as 2024-04-01. New versions ship on a monthly cadence when breaking changes exist, each supported for at least 12 months, followed by a 12-month deprecation split into full and limited support phases.
Ask about Gusto

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Gusto through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy