LedgerWire

Free tool

QuickBooks Web Connector .qwc file generator

Fill in your endpoint, get a valid .qwc file checked against the rules the Web Connector enforces. Free, no signup.

Valid. The Web Connector will accept this file.
Acme Sync.qwc
<?xml version="1.0"?>
<QBWCXML>
  <AppName>Acme Sync</AppName>
  <AppID></AppID>
  <AppURL>https://example.com/qbwc</AppURL>
  <AppDescription>Syncs Acme orders into QuickBooks Desktop</AppDescription>
  <AppSupport>https://example.com/support</AppSupport>
  <UserName>acme-customer-1</UserName>
  <OwnerID>{57F3B9B1-86F1-4FCC-B1EE-566DE1813D20}</OwnerID>
  <FileID>{90A44FB5-33D9-4815-AC85-BC87A7E7D1EB}</FileID>
  <QBType>QBFS</QBType>
  <Scheduler>
    <RunEveryNMinutes>5</RunEveryNMinutes>
  </Scheduler>
  <IsReadOnly>false</IsReadOnly>
</QBWCXML>

Generated in your browser; nothing is sent to LedgerWire. Don’t want to run the SOAP server yourself? A LedgerWire connection generates the .qwc, hosts the endpoint and gives you a REST API.

Questions

What is a .qwc file?

A small XML file that tells the QuickBooks Web Connector where your SOAP service lives (AppURL), which user name to authenticate with, and the OwnerID/FileID pair that identifies your app in the company file.

Why does the Web Connector reject my .qwc?

The usual reasons: AppURL is not HTTPS (only localhost may use HTTP), AppSupport is on a different domain from AppURL, or the OwnerID/FileID pair was already used in this company file (QBWC1039).

Should OwnerID and FileID be unique?

Use one OwnerID for your app and a new FileID per company file. Adding a .qwc whose OwnerID/FileID pair is already in that file fails with QBWC1039.

Related: QBWC1039, QBWC1012, qbXML to JSON converter, Web Connector guide.