How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Avalara MultiDocument API

Multi-document transaction management

Avalara MultiDocument API is one of 73 APIs that Avalara publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include MultiDocument. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.

This API exposes 11 operations across 10 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 3 base URLs: https://rest.avatax.com, https://sandbox-rest.avatax.com, http://{{baseurl}}.

11 operations 10 paths 3 schemas 4 GET7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Servers
https://rest.avatax.com
https://sandbox-rest.avatax.com
http://{{baseurl}}
Authentication
HTTP Basic, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Avalara MultiDocument API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). It accepts HTTP bearer tokens (bearerAuth).

  • basicAuth — Use your AvaTax username/password or accountId/licenseKey as basic auth credentials
  • bearerAuth — OAuth 2.0 bearer token

Paths & Operations 11

Across 10 paths, the API surfaces 11 operations — 4 GET, 7 POST. Each is listed below with its method, path, parameters, and response codes.

MultiDocument 11

Multi-document transaction management

POST
/api/v2/multidocument/transactions/create
Avalara Create a Multi-document Transaction
createMultiDocumentTransaction body → 200
POST
/api/v2/transactions/multidocument/{code}/type/{type}/adjust
Avalara AdjustMultiDocumentTransaction
4 params body → 200
GET
/api/v2/transactions/multidocument/{code}/type/{type}/audit
Avalara AuditMultiDocumentTransaction
3 params → 200
POST
/api/v2/transactions/multidocument/commit
Avalara CommitMultiDocumentTransaction
2 params body → 200
POST
/api/v2/transactions/multidocument
Avalara CreateMultiDocumentTransaction
2 params body → 200
GET
/api/v2/transactions/multidocument
Avalara ListMultiDocumentTransactions
1 param → 200
GET
/api/v2/transactions/multidocument/{code}/type/{type}
Avalara GetMultiDocumentTransactionByCodeAndType
3 params → 200
GET
/api/v2/transactions/multidocument/{id}
Avalara GetMultiDocumentTransactionById
2 params → 200
POST
/api/v2/transactions/multidocument/{code}/type/{type}/refund
Avalara RefundMultiDocumentTransaction
4 params body → 200
POST
/api/v2/transactions/multidocument/verify
Avalara VerifyMultiDocumentTransaction
2 params body → 200
POST
/api/v2/transactions/multidocument/{code}/type/{type}/void
Avalara VoidMultiDocumentTransaction
4 params body → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are AddressInfo (9 properties), MultiDocumentLineItemModel (7 properties), CreateMultiDocumentModel (2 properties). Each schema is shown below with its type and property counts.

AddressInfo
object
9 properties
MultiDocumentLineItemModel
object
7 properties
CreateMultiDocumentModel
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

avalara-multidocument-api-openapi.yml Raw ↑

Other APIs Avalara publishes across the network.

AvaTax SOAP API
Avalara Tax Content for Retail Configuration API
Self-Serve Tariff Classification API
License Guidance Order API
Avalara 1099 Forms API
Avalara Accounts API
Avalara Addresses API
Avalara AdvancedRules API
Avalara Attributes API
Avalara Authentication API
Avalara AvaFileForms API
Where this information came from

This is an independent, third-party profile of Avalara MultiDocument API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.