Avalara Logs allows users to check the status of certain jobs that are happening in the background of Ordway, as well as the history of actions taken. Logs are ideal for troubleshooting errors; what failed, how, and when.
Notes:
- Logs are currently available for view only.
- Logs are maintained for 90 days.
- Logs display in UTC Time Zone.
Steps:
Navigate to Menu > Operations > Logs > Avalara Logs.
Log Actions
View Log or Invoice
To view a specific log, click either the Status link or click View from the Actions menu. To view related objects with the log, click the corresponding hyperlink.
Sort
Sort available Logs by clicking the appropriate column header.
Filter Avalara Logs
Use the available Filter options to locate a specific API log. Learn more about Filtering Data in Ordway.
Log Details
Each log provides detailed information regarding the request. The top portion of each log contains the following:
Field |
Description |
ID |
Unique identifier assigned by Ordway for this log entry. |
Status |
Request status information. Error codes are available here: https://developer.avalara.com/avatax/errors/ |
Request Method |
Request method used in the log entry. Options include: GET DELETE |
Event |
The event or action within Ordway that causes the current request to be created and sent to Avalara. Examples: Create, Estimate, Tax, Delete, Edit |
Related Object |
Corresponding items related to this log. Examples: Invoice, Customer |
URL |
Endpoint of the log. |
Date |
Date the log was executed. |
Request query Parameters
When Ordway sends data to Avalara, either send an object with corresponding properties or send corresponding properties when the object is not known.
Generally sent via REST APIs as shown after the question mark in this example:
https://avalara/.../resolve_address?country=USA&zip=0000®ion=CA
in this case the query options are:
{
"country": "USA",
"zip": "0000",
"region": "CA"
}
Request Body Parameters
This section details the request sent by the Customer to Avalara.
Response Body
This section of the log details the response, including any error messages. Two error messages are indicated below.
Comments
0 comments
Please sign in to leave a comment.