LedgerWire

ItemService · Add

simulated in sandbox

ItemServiceAdd

Service items are labour and services you sell or buy. They carry either SalesOrPurchase (one account) or SalesAndPurchase (separate income and expense accounts).

qbXML request

ItemServiceAddRq
<?xml version="1.0" encoding="utf-8"?>
<?qbxml version="13.0"?>
<QBXML>
  <QBXMLMsgsRq onError="stopOnError">
    <ItemServiceAddRq requestID="1">
      <ItemServiceAdd>
        <Name>Site Survey</Name>
        <SalesOrPurchase>
          <Desc>Pre-install site survey</Desc>
          <Price>180.00</Price>
          <AccountRef>
            <FullName>Service Income</FullName>
          </AccountRef>
        </SalesOrPurchase>
      </ItemServiceAdd>
    </ItemServiceAddRq>
  </QBXMLMsgsRq>
</QBXML>

JSON equivalent

POST /v1/items
{
  "name": "Site Survey",
  "type": "service",
  "salesOrPurchase": {
    "desc": "Pre-install site survey",
    "price": 180,
    "accountRef": {
      "fullName": "Service Income"
    }
  }
}
curl
curl -X POST https://ledgerwire.vibiz.app/v1/items \
  -H "Authorization: Bearer $LEDGERWIRE_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Site Survey","type":"service","salesOrPurchase":{"desc":"Pre-install site survey","price":180,"accountRef":{"fullName":"Service 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)

ItemServiceAddRs
<?xml version="1.0" ?>
<QBXML>
  <QBXMLMsgsRs>
    <ItemServiceAddRs requestID="1" statusCode="0" statusSeverity="Info" statusMessage="Status OK">
      <ItemServiceRet>
        <ListID>80000019-1794881749</ListID>
        <TimeCreated>2026-04-29T03:44:37+00:00</TimeCreated>
        <TimeModified>2026-04-29T03:44:37+00:00</TimeModified>
        <EditSequence>1777434277</EditSequence>
        <Name>Site Survey</Name>
        <FullName>Installation</FullName>
        <IsActive>true</IsActive>
        <Sublevel>0</Sublevel>
        <SalesOrPurchase>
          <Desc>Pre-install site survey</Desc>
          <Price>180.00</Price>
          <AccountRef>
            <FullName>Service Income</FullName>
          </AccountRef>
        </SalesOrPurchase>
      </ItemServiceRet>
    </ItemServiceAddRs>
  </QBXMLMsgsRs>
</QBXML>

FAQ

What is required in ItemServiceAdd?

`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 ItemServiceAdd 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 ItemServiceAdd 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 ItemServiceAdd 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 ItemService messages

Other Add messages

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

Get a free sandbox key