Avalara AvaTax
Prepare filings from Avalara AvaTax with the numbers checked and the right person signing off.
25 ways to read, 6 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Avalara AvaTax, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create customer
customers.createApproval by rule - Create item
items.createApproval by rule - List exemption certificates
certificates.listRead
Example flow
- Avalara AvaTax · List exemption certificates
certificates.listDone - Avalara AvaTax · Create customer
customers.createMaker-checker - Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Avalara AvaTax.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Avalara AvaTax
- Avalara AvaTax's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a Avalara test account before you go live.
For developers
Technical detail
Read AvaTax transactions, companies, nexus, tax codes, items, customers, certificates and locations; record uncommitted transactions.
Avalara API docs- Source actions
- 25
- Destination actions
- 6
- Data types
- 19
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
address resolutions1
- Resolve addressSource
Validate and geocode a US or Canadian address and list the tax authorities for it. The address travels in the request body.
certificates2
- Get exemption certificateSource
Read one exemption certificate with its linked customers.
- List exemption certificatesSourceIncremental
List exemption certificates stored for the configured company.
companies1
- List companiesSourceIncremental
List the AvaTax companies this credential can see.
customer certificates1
- List a customer's certificatesSource
List the exemption certificates linked to one customer.
customers4
- Create customerDestinationNot retried automaticallyApproval before production
Create a customer so certificates and exemptions can be linked to its code.
- Get customerSource
Read one customer by customer code.
- List customersSourceIncremental
List exemption customers recorded for the configured company.
- Update customerDestinationProvider duplicate protectionApproval before production
Replace a customer's name, address and contact details.
economic nexus thresholds1
- Get economic nexus thresholdsSource
Read the company's economic nexus threshold status by state, as tracked by AvaTax.
filing frequencies1
- List filing frequenciesSource
List the filing frequencies AvaTax supports (monthly, quarterly and so on).
filing status1
- Get company filing statusSource
Read whether Avalara Managed Returns is filing for the configured company.
items4
- Create itemDestinationNot retried automaticallyApproval before production
Create a catalogue item with its tax code.
- Get itemSource
Read one item by its AvaTax item ID.
- List itemsSourceIncremental
List the product catalogue items AvaTax uses to choose tax codes.
- Update itemDestinationProvider duplicate protectionApproval before production
Replace an item's code, description and tax code.
locations2
- Get locationSource
Read one location by ID.
- List locationsSourceIncremental
List the company's reporting locations, storefronts and warehouses.
nexus2
- Get nexusSource
Read one nexus declaration by ID.
- List company nexusSourceIncremental
List the jurisdictions where the configured company declared nexus.
subscriptions1
- List account subscriptionsSource
List the Avalara services this account subscribes to.
system tax codes1
- List Avalara tax codesSource
List the Avalara-supported system tax codes, optionally by code prefix.
tax codes2
- Get company tax codeSource
Read one custom tax code by ID.
- List company tax codesSourceIncremental
List custom tax codes defined for the configured company.
tax companies1
- Read configured tax companySource
Authenticate against the company selected on this connection.
tax estimates1
- Calculate uncommitted sales taxDestinationNot retried automaticallyApproval before production
Calculate one fully taxable order line as SalesOrder. No invoice or filing is created.
tax rates1
- Get tax rates by postal codeSource
Read the combined sales tax rate and its jurisdiction parts for a US postal code.
transactions by id1
- Get transaction by IDSource
Read a transaction by its AvaTax transaction ID number.
transactions3
- Create uncommitted transactionDestinationNot retried automaticallyApproval before production
Record a sales, purchase or return document with full lines. Always sent with commit=false, so it is never reported until someone commits it in AvaTax.
- Get transaction by codeSource
Read the current version of a transaction by its code, with lines, tax summary and addresses.
- List transactionsSourceIncremental
List transactions recorded for the configured company code, with date, status, type and customer filters.
Access and limits
- Authentication
- Avalara account ID and license key
- Plans and access
- AvaTax account with API access. Exemption certificate APIs need certificate storage set up. Company access and the AvaTax role for each call (for example CompanyUser for reads, CompanyAdmin for item writes).
- Test environment
- Choose the Avalara sandbox and use its account ID and license key.
- Rate limits
- Respect AvaTax throttling (HTTP 429) and your account usage allowance. Transaction creation counts as billable AvaTax usage and is never automatically retried.
- Pagination
- Lists use $top/$skip with @recordsetCount (up to 1,000 records per page). Transaction lists default to the last 30 days unless a date filter is supplied.
- Provider events
- Not used by these operations. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Calculations require correct addresses, nexus, tax codes and amounts; Nexra does not determine tax liability.
- Transactions are only created uncommitted (commit=false). Commit, void, lock, adjust, refund, settle, change-code and uncommit are intentionally excluded.
- Deletes, nexus declarations, company creation, filing-status changes, certificate creation, uploads and customer-certificate linking are intentionally excluded.
- Tax rates by street address are excluded because AvaTax only accepts the address in the query string; use tax rates by postal code or address resolution (POST body) instead.
- Location create and update are excluded because locations drive reporting on filed returns; locations are read-only.
- Filing reads cover filing status, filing frequencies and economic nexus thresholds; Managed Returns worksheets and notices need separate Avalara products and are not implemented.
- Item and customer updates use PUT, which replaces the record: send every field you want to keep.
Developer reference
- Create the Avalara credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Avalara AvaTax, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/avalara-avatax and the Connections API.