LedgerWire

Vendor · Add

simulated in sandbox

VendorAdd

Vendors are who you buy from: suppliers, landlords, utilities and contractors. Bills and bill payments point at a vendor through VendorRef or PayeeEntityRef.

qbXML request

VendorAddRq
<?xml version="1.0" encoding="utf-8"?>
<?qbxml version="13.0"?>
<QBXML>
  <QBXMLMsgsRq onError="stopOnError">
    <VendorAddRq requestID="1">
      <VendorAdd>
        <Name>Allied Pipe &amp; Valve</Name>
        <CompanyName>Allied Pipe &amp; Valve</CompanyName>
        <VendorAddress>
          <Addr1>22 Industrial Pkwy</Addr1>
          <City>Tulsa</City>
          <State>OK</State>
          <PostalCode>74103</PostalCode>
        </VendorAddress>
        <Phone>(918) 555-0199</Phone>
        <NameOnCheck>Allied Pipe &amp; Valve</NameOnCheck>
      </VendorAdd>
    </VendorAddRq>
  </QBXMLMsgsRq>
</QBXML>

JSON equivalent

POST /v1/vendors
{
  "name": "Allied Pipe & Valve",
  "phone": "(918) 555-0199",
  "companyName": "Allied Pipe & Valve",
  "nameOnCheck": "Allied Pipe & Valve",
  "vendorAddress": {
    "city": "Tulsa",
    "addr1": "22 Industrial Pkwy",
    "state": "OK",
    "postalCode": "74103"
  }
}
curl
curl -X POST https://ledgerwire.vibiz.app/v1/vendors \
  -H "Authorization: Bearer $LEDGERWIRE_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Allied Pipe & Valve","phone":"(918) 555-0199","companyName":"Allied Pipe & Valve","nameOnCheck":"Allied Pipe & Valve","vendorAddress":{"city":"Tulsa","addr1":"22 Industrial Pkwy","state":"OK","postalCode":"74103"}}'

Run this request against your own sandbox

Add and Mod requests change data, so they run in a private sandbox, not the shared demo. Get a free key (10 seconds), then POST the request above to /v1/qbxml.

qbXML response (from the sandbox seed data)

VendorAddRs
<?xml version="1.0" ?>
<QBXML>
  <QBXMLMsgsRs>
    <VendorAddRs requestID="1" statusCode="0" statusSeverity="Info" statusMessage="Status OK">
      <VendorRet>
        <ListID>8000007D-1794881749</ListID>
        <TimeCreated>2025-11-07T00:23:19+00:00</TimeCreated>
        <TimeModified>2025-11-07T00:23:19+00:00</TimeModified>
        <EditSequence>1762474999</EditSequence>
        <Name>Allied Pipe &amp; Valve</Name>
        <IsActive>true</IsActive>
        <CompanyName>Allied Pipe &amp; Valve</CompanyName>
        <VendorAddress>
          <Addr1>22 Industrial Pkwy</Addr1>
          <City>Tulsa</City>
          <State>OK</State>
          <PostalCode>74103</PostalCode>
        </VendorAddress>
        <Phone>(918) 555-0199</Phone>
        <NameOnCheck>Allied Pipe &amp; Valve</NameOnCheck>
        <TermsRef>
          <FullName>Net 30</FullName>
        </TermsRef>
        <Balance>0.00</Balance>
      </VendorRet>
    </VendorAddRs>
  </QBXMLMsgsRs>
</QBXML>

FAQ

What is required in VendorAdd?

`name` at minimum. Elements must appear in the order the qbXML schema lists them; LedgerWire orders them for you when you send JSON.

Why does VendorAdd fail with status 3140?

3140 means a reference (for example ParentRef or an ItemRef) points at something that does not exist in the company file. Look the record up first, or create it, and pass its ListID.

Why does VendorAdd fail with status 3100?

The Name is already in use. QuickBooks requires unique names across customers, vendors, employees and other names, and within each item list. Query for the existing record and update it instead.

Sandbox fidelity

The LedgerWire sandbox simulates VendorAdd with QuickBooks rules: required fields, element names, refs that must exist (3140), unique names (3100), field lengths (3070) and EditSequence locking (3200). Tax calculation, custom fields and preferences are not simulated.

More Vendor messages

Other Add messages

Skip the XML: call POST /v1/vendors with JSON.

Get a free sandbox key