Reference · built on requestConnectorHR, scheduling & workforce

QuickBooks Time

Timesheets, users, jobcodes, schedule events, time off requests, and payroll reports from QuickBooks Time.

Request accessPricing ↗

About

QuickBooks Time, formerly TSheets, is Intuit's time tracking product for hourly and mobile crews, with a scheduler, GPS points, and approvals that feed payroll. Its REST API at rest.tsheets.com/api/v1 returns users, groups, jobcodes and jobcode assignments, timesheets, schedule calendars and events, time off requests, custom fields, geolocations, and reports for current totals and payroll.

Through Fibric, an operator polls last_modified_timestamps, reads what changed, and proposes a timesheet correction, an approval date, or a schedule event. You approve; the change is written once and a receipt records what changed and how to undo it.

This is a reference listing. It documents what Fibric would read from QuickBooks Time 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

  • Timesheets with start, end, duration, jobcode_id, on_the_clock, and locked through GET /timesheets, filtered by date range and user
  • Users with submitted_to, approved_to, pto_balances, and permissions through GET /users
  • Jobcodes and jobcode assignments, including type pto, through GET /jobcodes and GET /jobcode_assignments
  • Schedule events for a calendar through GET /schedule_events with schedule_calendar_ids and modified_since
  • Time off requests and entries with status pending, approved, denied, or canceled through GET /time_off_requests
  • Current totals per user, including on_the_clock and shift_seconds, and payroll totals through the /reports endpoints
  • Timesheets deleted in the last 180 days through GET /timesheets_deleted, and per-endpoint change times through /last_modified_timestamps

Proposed actions

  • Target capability: propose a timesheet through POST /timesheets or a correction through PUT /timesheets, up to 50 per batch
  • Target capability: propose moving a user's submitted_to or approved_to date through PUT /users when the Approvals Add-On is installed
  • Target capability: propose a schedule event through POST or PUT /schedule_events, up to 50 per batch
  • Target capability: propose a time off request status change through PUT /time_off_requests
  • Target capability: propose a notification to a user through POST /notifications, with an on_the_clock or off_the_clock precheck

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

What you can build

  • Close approvals before payroll runs

    Users carry submitted_to and approved_to. The operator lists who has not submitted through the period end, proposes reminders, and proposes the approved_to update once a manager signs off.

    With Timesheet Signoff

  • Catch overtime as it accrues

    The current totals report gives shift_seconds and on_the_clock per user, and the payroll report gives total_ot_seconds. The operator proposes who to send home or reassign before the threshold.

    With Overtime Guard

  • Reconcile punches with the schedule

    Schedule events give the planned start; timesheets give the actual. The operator proposes the mismatches for a manager to correct, with the timesheet edit ready to apply.

    With Punch Match, Missed Punch

  • Keep labor against the jobcode budget

    Payroll by jobcode totals hours per job. The operator proposes where a job is running past its estimate and which timesheets drove it.

    With Labor Budget

Requirements

  • A QuickBooks Time account with the API Add-On installed under Feature Add-ons
  • An API application created under Feature Add-ons → API → Add a new application, giving a client_id and client_secret
  • A user who authorizes the app through the OAuth flow; the token carries that user's permissions
  • TLS on every request; unencrypted HTTP is not supported
Authentication
OAuth 2.0 authorization code flow against /authorize and /grant for an API application created under Feature Add-ons → API, with access tokens refreshed before they expire.

Limits

  • Requests are limited to 300 calls in any 5 minute window per access token; the API returns 429 until the window passes
  • Responses return at most 200 results per page; follow the more flag with the page parameter
  • No webhooks are documented; change detection polls last_modified_timestamps and modified_since
  • An API application may connect to 3 client accounts besides your own by default; wider use is arranged with Intuit

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 QuickBooks Time ↗

Questions and answers

Does QuickBooks Time send webhooks?
No. The documentation has no webhook mechanism. It recommends querying the last_modified_timestamps endpoint to see when any object on an endpoint last changed, then calling that endpoint with modified_since. Deleted timesheets remain readable through /timesheets_deleted for 180 days.
How do I know who is on the clock right now?
Query /timesheets for the user with on_the_clock=yes and a start_date seven days back; a result means they are clocked in, because the service auto-clocks out anyone after 7 days on the clock. The current totals report returns on_the_clock and shift_seconds for every user.
What stops a timesheet from being edited?
A locked value greater than 0 means the timesheet is locked, for example after export or invoicing, and locked does not reflect submitted or approved status. Deleting a timesheet is permanent; the documentation advises deleting only to correct an inaccuracy.
Ask about QuickBooks Time

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 QuickBooks Time 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