# Vendor record management

Source: https://developer.avalara.com/avatax-for-ap/zzz8641313095324/

# Vendor record management

Manage vendor records through the AvaTax API so vendor changes in the source application stay synchronized with AvaTax.

**Element type:** Required

**Endpoints/models used:** [CreateVendor](https://developer.avalara.com/products/avatax/api/methods/Vendors/CreateVendors/), [GetVendor](https://developer.avalara.com/products/avatax/api/methods/Vendors/GetVendor/), [UpdateVendor](https://developer.avalara.com/products/avatax/api/methods/Vendors/UpdateVendor/), [DeleteVendor](https://developer.avalara.com/products/avatax/api/methods/Vendors/DeleteVendor/), [QueryVendors](https://developer.avalara.com/products/avatax/api/methods/Vendors/QueryVendors/)

Your integration must manage vendor records through the AvaTax API rather than requiring manual entry in the AvaTax portal. When a vendor is created, updated, or removed in the source application, that change is reflected in AvaTax through the corresponding API call rather than a manual step.

-   When a new vendor is added in the source application, call [CreateVendor](https://developer.avalara.com/products/avatax/api/methods/Vendors/CreateVendors/) to create the matching vendor record in AvaTax.

-   When vendor details change in the source application, call [UpdateVendor](https://developer.avalara.com/products/avatax/api/methods/Vendors/UpdateVendor/) to keep the AvaTax record current.

-   Before creating a new vendor record, use [QueryVendors](https://developer.avalara.com/products/avatax/api/methods/Vendors/QueryVendors/) or [GetVendor](https://developer.avalara.com/products/avatax/api/methods/Vendors/GetVendor/) to check whether the vendor already exists, to avoid duplicate records.

-   When a vendor is removed in the source application, call [DeleteVendor](https://developer.avalara.com/products/avatax/api/methods/Vendors/DeleteVendor/) to remove or deactivate the corresponding AvaTax record.

Both updates add 1 consolidated requirement for API based vendor record management, keeping the certification badge and integration guide aligned with the released Vendor CRUD API functionality. Certification requirements and integration guide language use the same requirement wording so partners see consistent expectations across both documents.