Skip to main content
Use the @bijection/connectors/quickbooks-time entrypoint to declare QuickBooks Time resources.

​
Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

​
Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

​
Timesheets

​
changes: Timesheets modified since the last pass, with deletions

The following example matches configuration standard.

​
Configuration: standard

Case: quickbooks-time/timesheets/changes/standard. Connection and resource configuration are declared by this exact case. Credential kind: quickbooks-time. Keep credential material in the private credential inventory. Inspect the complete configuration contract below for settings and conditional requirements.
Native admission analysis is available for this exact declaration. Collection: timesheets
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. QuickBooks Time was TSheets; its API is still https://rest.tsheets.com/api/v1/. An OAuth 2 access token, sent as Authorization: Bearer (an OAuth bearer envelope), authorizes; tokens made in the API add-on’s preferences work the same way. The account is the company’s client_url, read from GET /current_user, because the user object names no company id. timesheets.changes reads the timesheets modified since the last pass, active ones included (on_the_clock=both), without supplemental data, and then the deleted timesheets since the last pass. Each listing answers results.timesheets (or results.timesheets_deleted) as an object keyed by id; the response contract turns it into the array of its members before anything reads it. The listing pages by number in an order the reference does not state, and page numbers over a live result skip a row when an earlier one is deleted or moves. So a pass reads windows of modification time instead (modified_since with modified_before) and accepts a window only when one response holds it (more: false), halving a full window until it fits 200 rows. The first request of a pass is open-ended; when it holds everything the pass is one request, otherwise its Date header fixes the instant the windows run up to. The next pass starts five minutes before that instant, so a timesheet saved during a pass is read by the next one. Only a single second holding more than 200 changed timesheets, as a bulk import can produce, is paged by number, and an edit or deletion during that paging can skip one of its rows. Deleted timesheets are kept 180 days. The deleted listing is read from the previous pass’s deletion bound, or from the live listing’s instant on a first pass; a source whose deletion bound is older than 180 days refuses its pass and must be rebaselined. A timesheet’s version is its last_modified text, which has second precision, so two saves within one second share a version. Published fields are the id, user and jobcode ids, type, start, end, date, duration (seconds), whether it is on the clock, the lock flag, notes, the custom field values as JSON text, and last_modified. Not confirmed in the reference: whether modified_since includes its own instant (each window asks from one second earlier), whether the deleted listing’s last_modified is the deletion time, and whether the response order is stable. Nothing is written. Built from the provider’s published API documentation; nothing here has run against QuickBooks Time or been qualified.

​
Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

​
Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.