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 Customers API

Manage customer records and their certificate associations

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

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

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

18 operations 13 paths 4 schemas 1 DELETE8 GET5 POST4 PUT

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
https://api.certcapture.com/v2
http://{{baseurl}}
Authentication
HTTP Basic, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Avalara Customers 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 18

Across 13 paths, the API surfaces 18 operations — 1 DELETE, 8 GET, 5 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

Customers 18

Manage customer records and their certificate associations

GET
/api/v2/companies/{companyId}/customers
Avalara List Customers for a Company
queryCustomers 4 params → 200
POST
/api/v2/companies/{companyId}/customers
Avalara Create a New Customer
createCustomer 1 param body → 201
GET
/customers
Avalara List Customers
listCustomers 2 params → 200
POST
/customers
Avalara Create a Customer
createCustomer body → 201
GET
/customers/{customerId}
Avalara Get a Customer by ID
getCustomer 1 param → 200
PUT
/customers/{customerId}
Avalara Update a Customer
updateCustomer 1 param body → 200
GET
/customers/{customerId}/certificates
Avalara List Certificates for a Customer
getCustomerCertificates 1 param → 200
DELETE
/api/v2/companies/{companyId}/customers/{customerCode}
Avalara DeleteCustomer
3 params → 200
GET
/api/v2/companies/{companyId}/customers/{customerCode}
Avalara GetCustomer
3 params → 200
PUT
/api/v2/companies/{companyId}/customers/{customerCode}
Avalara UpdateCustomer
4 params body → 200
PUT
/api/v2/companies/{companyId}/customers/{customerCode}/attributes/link
Avalara LinkAttributesToCustomer
4 params body → 200
POST
/api/v2/companies/{companyId}/customers/{customerCode}/certificates/link
Avalara LinkCertificatesToCustomer
4 params body → 200
POST
/api/v2/companies/{companyId}/customers/billto/{code}/shipto/link
Avalara LinkShipToCustomersToBillCustomer
4 params body → 200
GET
/api/v2/companies/{companyId}/customers/{customerCode}/attributes
Avalara ListAttributesForCustomer
3 params → 200
GET
/api/v2/companies/{companyId}/customers/{customerCode}/certificates
Avalara ListCertificatesForCustomer
3 params → 200
GET
/api/v2/companies/{companyId}/customers/{customerCode}/certificates/{country}/{region}
Avalara ListValidCertificatesForCustomer
5 params → 200
PUT
/api/v2/companies/{companyId}/customers/{customerCode}/attributes/unlink
Avalara UnlinkAttributesFromCustomer
4 params body → 200
POST
/api/v2/companies/{companyId}/customers/{customerCode}/certificates/unlink
Avalara UnlinkCertificatesFromCustomer
4 params body → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are CustomerModel (11 properties), CertCaptureCustomer (10 properties), CustomerListResponse (2 properties), FetchResult_CustomerModel (2 properties). Each schema is shown below with its type and property counts.

FetchResult_CustomerModel
object
2 properties
CustomerModel
object
11 properties
CertCaptureCustomer
object
10 properties
CustomerListResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

avalara-customers-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 Customers 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.