Author: Vishal Aggarwal

View all

August 24, 2015 | Vishal Aggarwal

.NET SDK v2.3 for QuickBooks Now Available

We are excited to announce the availability of the .NET SDK v2.3 for QuickBooks. This version of the SDK includes the addition of several new entities, as well as bug fixes. Accounting – Capability to Email Invoice, Estimate, and SalesReceipt objects. The format of the email content….. Read more

July 28, 2015 | Vishal Aggarwal

PHP SDK v2.1 for QuickBooks Online Now Available

Today we are happy to announce the availability of v2.1 of the PHP SDK for QuickBooks. This version of the SDK includes addition of several new entities as well as bug fixes. Accounting Look for these improvements: TaxService entity added. Provides ability to create TaxCode and….. Read more

June 16, 2015 | Vishal Aggarwal

Canada and India Sandbox Now Available!

As a follow up to the “Sandbox Goes Global” announcement, today we are happy to announce the support for Canada (CA) and India (IN) regions in our QuickBooks Online Sandbox developer environment. The addition of Canada and India now takes the regions supported in the sandbox environment….. Read more

May 18, 2015 | Vishal Aggarwal

Sandbox Goes Global

Today we’re excited to announce that our QuickBooks Online Sandbox developer environment now supports Australia (AU) and United Kingdom (UK) regions. The QuickBooks Online sandbox environment, launched last year at QuickBooks Connect, gives developers a ready-to-use, sandbox company for development and testing purposes, including sample data... Read more

March 20, 2015 | Vishal Aggarwal

Publishing on QuickBooks Now Easier

We’ve heard your feedback! A lot of you have provided input on the publishing process for QuickBooks We’re working hard to meet your needs and have made an important change to the requirements for publishing on What’s new Apps published on QuickBooks must….. Read more

March 16, 2015 | Vishal Aggarwal

Reports API: Upcoming fix in date format

We have had a lot of developers report a bug about the format of date returned from the reports API response. Even though the reports API specification mentions that all dates are in YYYY-MM-DD format, this does not hold good for cases where company settings are modified to use….. Read more