LedgerWire

Employee · Query

production passthrough only

EmployeeQuery

Employees share the name space with customers and vendors. Payroll and time-tracking syncs read them.

qbXML request

EmployeeQueryRq
<?xml version="1.0" encoding="utf-8"?>
<?qbxml version="13.0"?>
<QBXML>
  <QBXMLMsgsRq onError="stopOnError">
    <EmployeeQueryRq requestID="1">
      <ActiveStatus>ActiveOnly</ActiveStatus>
    </EmployeeQueryRq>
  </QBXMLMsgsRq>
</QBXML>

JSON equivalent

POST /v1/qbxml
POST /v1/qbxml

Sent unchanged through the Web Connector in production. The hosted sandbox does not simulate this message yet and answers status 3250.

curl
curl -X POST https://ledgerwire.vibiz.app/v1/qbxml \
  -H "Authorization: Bearer $LEDGERWIRE_KEY" \
  -H "Content-Type: application/xml" \
  --data-binary @employeequery.xml
Sends this exact qbXML to the shared demo sandbox (simulated sample data).

qbXML response

EmployeeQueryRs
<?xml version="1.0" ?>
<QBXML>
  <QBXMLMsgsRs>
    <EmployeeQueryRs requestID="1" statusCode="0" statusSeverity="Info" statusMessage="Status OK">
      <!-- EmployeeRet with the record QuickBooks stored -->
      </EmployeeQueryRs>
    </QBXMLMsgsRs>
  </QBXML>

FAQ

Can I send EmployeeQuery 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 EmployeeQuery?

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 EmployeeQuery yet and answers statusCode 3250 saying so. In production it is passed to QuickBooks unchanged.

Other Query messages

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

Get a free sandbox key