Skip to main content
Use the @bijection/connectors/quickbooks entrypoint to declare QuickBooks Online 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.

Accounting entities

pull: Query walk, CDC changes and tombstones, SyncToken-conditioned sparse updates

The following example matches configuration standard.
The function references identify application policy queries. Implement those policies in your application; the references alone grant no authority.

Configuration: standard

Case: quickbooks/entities/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: quickbooks. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Commands
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: readOnly

Case: quickbooks/entities/pull/readOnly. Connection and resource configuration are declared by this exact case. Credential kind: quickbooks. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
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. One CDC-readable entity of one company. Setup realmId; the connection holds a quickbooks credential (quickbooks.credential), an OAuth 2.0 grant for https://quickbooks.api.intuit.com (environment: "sandbox" for the sandbox host). Every request sends minorversion=75. The first pass walks the entity through the query endpoint by STARTPOSITION (name lists include inactive members). Later passes send one cdc?changedSince= request from five minutes before the server time the previous pass answered at, and every fullEvery-th pass walks again. Each record publishes id, syncToken (its version), createTime, lastUpdatedTime, the selected fields, and currency beside any amount. Amounts are exact decimal text: QuickBooks writes them as JSON numbers at two decimals, within the 15 significant digits a double keeps exactly. Deletion is CDC’s status: "Deleted" only. A voided transaction is an update and stays present. A CDC answer holding 1,000 objects (its stated cap, with no paging) refuses the pass, and CDC reads back 30 days: either stuck state needs the source’s carried position reset, after which deletions inside the gap are not observed. update is a sparse update carrying the published SyncToken; QuickBooks refuses a stale one (fault 5010), so the write applies only to the version it was decided against. requestid states no retention, so delivery is a single attempt and a lost answer stays unknown. updates: "webhooks" admits Intuit’s signed CloudEvents deliveries (intuit-signature) as refresh hints. Intuit sends every entity and company of an app to one URL, so at most one collection per app receives them. Nothing here has run against QuickBooks or been qualified. See the platform’s llm-wiki/wiki/providers/accounting.md.

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.