How To Create A .qwc File For QuickBooks Web Connector

In this blog, we are going to create a .qwc file for QuickBooks Web Connector. QuickBooks Web Connector is a desktop application that sync/exchange data with QuickBooks Desktop products.
using QuickBooks Web Connector we can transfer data between web API/applications and QuickBooks Desktop. It supports two-way sync, e.x: transfer data from the web to QuickBooks, and transfer data from QuickBooks to the web.

It’s recommended way to connect websites to QuickBooks. as compare to IIF files or CSV/Excel imports/exports.

So for communication between web applications and QuickBooks Desktop, we need to add a .qwc file in QuickBooks Web Connector.

You can create a .qwc file in notepad or in any text editor, you just need to save it with the .qwc extension.

Below is a sample QWC File

<?xml version="1.0"?>
<QBWCXML>
<AppName>Custonmer Demo WebService</AppName>
<AppID>1</AppID>
<AppURL>https://www.domain.com/quickbooks/CustomerWebService.asmx</AppURL>
<AppDescription>A short informative description for WebService</AppDescription>
<AppSupport>http://developer.intuit.com</AppSupport>
<UserName>User123</UserName>
<OwnerID>{67A3B9B1-56F1-4fcc-B1TE-666DE1813D26}</OwnerID>
<FileID>{23A44EB5-33D9-4815-AG85-BC87A7E7D1XY}</FileID>
<QBType>QBFS</QBType>
<Scheduler>
<RunEveryNMinutes>2</RunEveryNMinutes>
</Scheduler>
</QBWCXML>

Below are details of the QWC XML Element,

AppName – (Required – Yes) – This name will be displayed to the user in the QB Web Connector GUI.

AppID – (Required – Yes – can be empty) – It’s an AppID of the application, it should be unique, if we don’t want to pass AppID then we can supply only the tag without supplying any value in it.

AppURL – (Required – Yes) – In this, we have to provide our web API/Applications/Service URL. it must be a valid URL. It must have to be HTTPS, or else the Web connector will not connect. for development and testing, we can use localhost.

AppDescription – (Required – Yes) – We can provide a short description that will be displayed below AppName to the user in the QB Web Connector GUI. we can also only supply the tag without supplying any value in it.

AppSupport – (Required – Yes) – In this, we have to provide our website URL where users can go for support for our application. AppSupport URL must match the same domain name used in the AppURL.

UserName – (Required – Yes) – UserName will be used for accessing our web API/Applications/Service. UserName will be passed When the QB Web Connector calls the authenticate method on your web service.

OwnerID – (Required – Yes) – It is a GUID that represents our application. we should generate one GUID per application and it should be unique for each application.

FileID – (Required – Yes) – Same as above.

QBType – (Required – Yes) – We need to Specifies the type of Quickbooks which we want to connect to with the web connector (EX:- “QBFS” or “QBPOS”).

Scheduler – (Required – No) – It is an optional tag. We can use this to schedule the QB Web Connector to run automatically at specific intervals.

Hope this information will help you. For more QuickBooks-related articles you can visit my profile.

Tabish Rangrej

Tabish Rangrej is an Experienced .NET Team Leader, software engineer, and Author with a demonstrated history of working in the IT industry. He has quite well experience in developing, communicating, managing, and writing in his field. He has strong skills and knowledge of ASP.NET C#, ASP.NET MVC, ASP.NET CORE, Angular, AngularJS, Web API, SQL, Entity Framework, JavaScript, Jquery, Different Integrations like Quickbooks, Stripe, Google APIs, Zoho, Orion, Xero, etc., Different versioning tools like TFS, SVN, GIT, etc. and Windows services. Strong engineering professional with a Master of Computer Applications - MCA focused on Computer Science from Veer Narmad South Gujarat University, Surat. Tabish is always ready to accept new challenges and learn new things, he would like to serve better for the community.