LedgerWire

ItemNonInventory · Add

simulated in sandbox

ItemNonInventoryAdd

Non-inventory items are things you sell or buy without tracking stock: special orders, supplies or pass-through fees.

qbXML request

ItemNonInventoryAddRq
<?xml version="1.0" encoding="utf-8"?>
<?qbxml version="13.0"?>
<QBXML>
  <QBXMLMsgsRq onError="stopOnError">
    <ItemNonInventoryAddRq requestID="1">
      <ItemNonInventoryAdd>
        <Name>Job Signage</Name>
        <SalesOrPurchase>
          <Desc>Temporary job signage</Desc>
          <Price>30.00</Price>
          <AccountRef>
            <FullName>Sales Income</FullName>
          </AccountRef>
        </SalesOrPurchase>
      </ItemNonInventoryAdd>
    </ItemNonInventoryAddRq>
  </QBXMLMsgsRq>
</QBXML>

JSON equivalent

POST /v1/items
{
  "name": "Job Signage",
  "type": "nonInventory",
  "salesOrPurchase": {
    "desc": "Temporary job signage",
    "price": 30,
    "accountRef": {
      "fullName": "Sales Income"
    }
  }
}
curl
curl -X POST https://ledgerwire.vibiz.app/v1/items \
  -H "Authorization: Bearer $LEDGERWIRE_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Job Signage","type":"nonInventory","salesOrPurchase":{"desc":"Temporary job signage","price":30,"accountRef":{"fullName":"Sales Income"}}}'

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)

ItemNonInventoryAddRs
<?xml version="1.0" ?>
<QBXML>
  <QBXMLMsgsRs>
    <ItemNonInventoryAddRs requestID="1" statusCode="0" statusSeverity="Info" statusMessage="Status OK">
      <ItemNonInventoryRet>
        <ListID>80000046-1794871862</ListID>
        <TimeCreated>2026-04-10T20:27:05+00:00</TimeCreated>
        <TimeModified>2026-04-10T20:27:05+00:00</TimeModified>
        <EditSequence>1775852825</EditSequence>
        <Name>Job Signage</Name>
        <FullName>Misc Hardware</FullName>
        <IsActive>true</IsActive>
        <Sublevel>0</Sublevel>
        <SalesOrPurchase>
          <Desc>Temporary job signage</Desc>
          <Price>30.00</Price>
          <AccountRef>
            <FullName>Sales Income</FullName>
          </AccountRef>
        </SalesOrPurchase>
      </ItemNonInventoryRet>
    </ItemNonInventoryAddRs>
  </QBXMLMsgsRs>
</QBXML>

FAQ

What is required in ItemNonInventoryAdd?

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

Why does ItemNonInventoryAdd 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 ItemNonInventoryAdd 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 ItemNonInventoryAdd 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 ItemNonInventory messages

Other Add messages

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

Get a free sandbox key