Transaction · Del
production passthrough onlyTxnDel
TxnDel deletes a transaction by type and TxnID. It cannot be undone, so most integrations void instead (TxnVoid).
qbXML request
<?xml version="1.0" encoding="utf-8"?>
<?qbxml version="13.0"?>
<QBXML>
<QBXMLMsgsRq onError="stopOnError">
<TxnDelRq requestID="1">
<TxnDelType>Invoice</TxnDelType>
<TxnID>1F4-1731000000</TxnID>
</TxnDelRq>
</QBXMLMsgsRq>
</QBXML>JSON equivalent
POST /v1/qbxmlSent unchanged through the Web Connector in production. The hosted sandbox does not simulate this message yet and answers status 3250.
curl -X POST https://ledgerwire.vibiz.app/v1/qbxml \
-H "Authorization: Bearer $LEDGERWIRE_KEY" \
-H "Content-Type: application/xml" \
--data-binary @txndel.xmlRun 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
<?xml version="1.0" ?>
<QBXML>
<QBXMLMsgsRs>
<TxnDelRs requestID="1" statusCode="0" statusSeverity="Info" statusMessage="Status OK">
<!-- TransactionRet with the record QuickBooks stored -->
</TxnDelRs>
</QBXMLMsgsRs>
</QBXML>FAQ
Can I send TxnDel through LedgerWire?
Yes, in production: POST the qbXML to /v1/qbxml with a live key and it is passed to QuickBooks through the Web Connector unchanged.
Does the sandbox simulate TxnDel?
Not yet. The sandbox answers it with statusCode 3250 and a message saying so, rather than inventing a response. The ten core objects are fully simulated.
Which QuickBooks editions support it?
All current desktop editions (Pro, Premier, Accountant and Enterprise) support it.
Sandbox fidelity
The sandbox does not simulate TxnDel yet and answers statusCode 3250 saying so. In production it is passed to QuickBooks unchanged.
Other Del messages
Skip the XML: call POST /v1/qbxml with JSON.
Get a free sandbox key