VendorAdd qbXML example
Adds a vendor.
qbXML
VendorAddRq, version 16.0
<?xml version="1.0" encoding="utf-8"?>
<?qbxml version="16.0"?>
<QBXML>
<QBXMLMsgsRq onError="stopOnError">
<VendorAddRq>
<VendorAdd>
<Name>Northwind Supplies</Name>
<CompanyName>Northwind Supplies</CompanyName>
<VendorAddress>
<Addr1>48 Harbor Rd</Addr1>
<City>Portland</City>
<State>OR</State>
<PostalCode>97201</PostalCode>
</VendorAddress>
<Phone>555-0100</Phone>
<Email>orders@northwind.example</Email>
<TermsRef>
<FullName>Net 30</FullName>
</TermsRef>
</VendorAdd>
</VendorAddRq>
</QBXMLMsgsRq>
</QBXML>
Open in the validator
Check it against the qbXML 16.0 schema, edit it, and run it in your own QuickBooks.
Things to know
- Elements must appear in the order the schema lists them: a valid element in the wrong place fails validation.
- Write a character above ASCII (é, ©, a curly quote) as a numeric reference such as é. Written as itself, it fails the whole document.
- Name must be unique among customers, vendors, employees and other names.
The same request with QuBe Sync's API
QuBe Sync takes this JSON, writes the qbXML for you and delivers QuickBooks' answer to your webhook as JSON.
POST
/api/v2/connections/{connection_id}/vendors
{
"company_name": "Northwind Supplies",
"email": "orders@northwind.example",
"name": "Northwind Supplies",
"phone": "555-0100",
"terms_ref": {
"full_name": "Net 30"
},
"vendor_address": {
"addr1": "48 Harbor Rd",
"city": "Portland",
"postal_code": "97201",
"state": "OR"
}
}
Every field VendorAdd takes is in Intuit's reference.
More requests
Vendors and purchases