Account · Add
simulated in sandboxAccountAdd
Accounts make up the chart of accounts: banks, AR and AP, income, cost of goods sold and expenses. Every transaction line ultimately points at one.
qbXML request
<?xml version="1.0" encoding="utf-8"?>
<?qbxml version="13.0"?>
<QBXML>
<QBXMLMsgsRq onError="stopOnError">
<AccountAddRq requestID="1">
<AccountAdd>
<Name>Shop Equipment</Name>
<AccountType>FixedAsset</AccountType>
<AccountNumber>1550</AccountNumber>
<Desc>Tools and shop equipment</Desc>
</AccountAdd>
</AccountAddRq>
</QBXMLMsgsRq>
</QBXML>JSON equivalent
{
"desc": "Tools and shop equipment",
"name": "Shop Equipment",
"accountType": "FixedAsset",
"accountNumber": "1550"
}curl -X POST https://ledgerwire.vibiz.app/v1/accounts \
-H "Authorization: Bearer $LEDGERWIRE_KEY" \
-H "Content-Type: application/json" \
-d '{"desc":"Tools and shop equipment","name":"Shop Equipment","accountType":"FixedAsset","accountNumber":"1550"}'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)
<?xml version="1.0" ?>
<QBXML>
<QBXMLMsgsRs>
<AccountAddRs requestID="1" statusCode="0" statusSeverity="Info" statusMessage="Status OK">
<AccountRet>
<ListID>80000001-1760311862</ListID>
<TimeCreated>2025-10-12T23:31:02+00:00</TimeCreated>
<TimeModified>2025-10-12T23:31:02+00:00</TimeModified>
<EditSequence>1760311862</EditSequence>
<Name>Shop Equipment</Name>
<FullName>Checking</FullName>
<IsActive>true</IsActive>
<Sublevel>0</Sublevel>
<AccountType>FixedAsset</AccountType>
<AccountNumber>1550</AccountNumber>
<Desc>Tools and shop equipment</Desc>
<Balance>48210.37</Balance>
<TotalBalance>48210.37</TotalBalance>
</AccountRet>
</AccountAddRs>
</QBXMLMsgsRs>
</QBXML>FAQ
What is required in AccountAdd?
`name`, `accountType` at minimum. Elements must appear in the order the qbXML schema lists them; LedgerWire orders them for you when you send JSON.
Why does AccountAdd 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 AccountAdd 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 AccountAdd 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 Account messages
Skip the XML: call POST /v1/accounts with JSON.
Get a free sandbox key