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 Electronic Invoices API

Issue and manage electronic fiscal documents

Avalara Electronic Invoices 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 Electronic Invoices. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.

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

Requests are made against a single base URL, https://avataxbr-sandbox.avalarabrasil.com.br/v3.

4 operations 3 paths 4 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Server
https://avataxbr-sandbox.avalarabrasil.com.br/v3
Authentication
HTTP Bearer
License
Terms of Service
Resource Areas
1

Authentication & Security 1

Avalara Electronic Invoices API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Bearer token authentication

Paths & Operations 4

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

Electronic Invoices 4

Issue and manage electronic fiscal documents

POST
/invoices
Avalara Issue an Electronic Invoice
createInvoice body → 201
GET
/invoices
Avalara List Electronic Invoices
listInvoices 5 params → 200
GET
/invoices/{invoiceId}
Avalara Get an Invoice by ID
getInvoice 1 param → 200
POST
/invoices/{invoiceId}/cancel
Avalara Cancel an Electronic Invoice
cancelInvoice 1 param body → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are InvoiceLine (7 properties), InvoiceResponse (7 properties), BrazilParty (6 properties), InvoiceRequest (5 properties). Each schema is shown below with its type and property counts.

InvoiceResponse
object
7 properties
BrazilParty
object
6 properties
InvoiceRequest
object
5 properties
InvoiceLine
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

avalara-electronic-invoices-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 Electronic Invoices 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.