AvaTax for Communications
Communications REST v2 Dev Guide
Getting Started
Calculate Taxes
Commit/Uncommit
Customizing Transactions
Account Customizations
Transaction Use Cases
- Simple Request
- Multi-line Request
- Jurisdiction Determination
- Interstate/Intrastate Determination
- Tax Override
- Safe Harbor Override
- Private Line
- Proration
- Transaction Information
- Exclusions
- Transaction-Level Commit/Uncommit
- Invoice Date
- Invoice Mode
- Optional Fields
- Adjustments
- Tax Inclusive
- Displaying Tax Results
- Quantity
- Request Config
Exemptions
Sales and Use
Jurisdiction Determination Use Cases
Reference
Calculating Tax Offline
AvaTax for Communications Use Cases
FAQ
Chapter 6.1 - Detecting a Dropped Connection
Errors related to offline tax calculation can be complex when the connection has dropped. Errors are generated from different locations:
- Communications REST v2
- The operating system
- Your software development suite
A dropped connection produces a different kind of error - for example, AspNetCore produces a WinHttpException when a connection is dropped using HttpClient. Your task is to identify how the operating system or programming language exposes a connection error. Once you have identified this error, your code must trap the exception, ensure that you can respond correctly, and prevent the exception from being exposed to the end user or calling system.