Skip to main content
Use the @bijection/connectors/avalara entrypoint to declare Avalara AvaTax 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.

​
Transactions

​
pull: modifiedDate keyset with commit and void transitions

The following example matches configuration standard.

​
Configuration: standard

Case: avalara/transactions/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: avalara. 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: transactions
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Configuration: transitions

Case: avalara/transactions/pull/transitions. Connection and resource configuration are declared by this exact case. Credential kind: avalara. 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: transactions
Commands
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. The connection holds an avalara Basic credential (account id and license key) for rest.avatax.com or sandbox-rest.avatax.com. Identity is /api/v2/utilities/ping’s authenticatedAccountId; ping answers 200 without credentials too, so authenticated: true is required. transactions.pull lists one company’s transactions with $filter=date ge '1900-01-01' and status ne 'Adjusted' and modifiedDate ge '<t>' (a listing without a date criterion reads only 30 days), $orderBy=modifiedDate ASC, $top=1000. There is no $skip: an offset into a set that changes while it is paged skips a row, so each page filters from the last modifiedDate the previous page returned, re-reading the boundary and deduplicating by modifiedDate. A full page sharing one modifiedDate is refused. A page shorter than 1,000 ends the pass, which carries the latest modifiedDate; the next pass reads from five minutes before it. A record is a document keyed by (code, type). Adjusted versions are filtered out, so an adjustment moves the record to its new version; a voided document stays present with status Cancelled; nothing is withdrawn. AvaTax writes totalAmount, totalTaxable and totalTax as JSON numbers, kept as the shortest round-trip text and never as exact decimals. With governingRule, commit ({commit: true}) and void (&#123;code: "DocVoided"&#125;) are state transitions addressed by the document’s code and type, so a repeat cannot create a document. Each declares a target-state condition: CannotModifyLockedTransaction, InvalidDocumentStatus, TransactionIsCommitted (commit) and TransactionAlreadyCancelled (void) read as a lost conditional write. AvaTax has no idempotency key, so each is one attempt and a lost answer stays unknown; the read-back says what is true now, not whose transition made it so. Company and document codes travel in route segments in AvaTax’s own escaped spelling, which the host renders: /, +, ?, % and # become _-ava2f-_, _-ava2b-_, _-ava3f-_, _-ava25-_ and _-ava23-_, and a space is sent as %20, so any code is addressable. Nothing here has run against Avalara 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.