The "minimul" QuickBooks Online API Guide
Last updated on 2017-10-07
About the Book
The first goals of most QuickBooks Online integration projects is not only getting connected but to import and persist important QuickBooks entities like customers, vendors, items, etc. You will be surprised how many details you need to know in order to do these aims properly avoiding a poor foundation, which will lead to many bugs and support tickets down the road. Learn these precious integration gems from a seasoned QuickBooks integration professional and in the process enjoy saving money and time by erecting a fantastic groundwork that will make your app soar in profitability.
Constituting and persisting the QuickBooks API connection
- Database columns for persisting OAuth credentials
- Encrypting Persisted OAuth information
- Setting the stage for OAuth auto-renewing
- Sensitive Information in Rails
- Important libraries
Properly handling OAuth
- Basic OAuth2 flow
- The redirect_uri
The QuickBooks Connect Button
- Note on Turbolinks
- Connect button page code
- Click the “Connect” button
- Auto-renew the OAuth credentials
- In the Background
- Importing Customers and Vendors
Advanced QBO Customer and Vendor Importing
- Why not just key off of the QBO Id?
- OK, I get that the DisplayName is important but then why record the QBO Id?
- Using an existing column to sync the DisplayName.
- Parsing deeply nested JSON
When would I need to use
Importing the Chart of Accounts
- Important attributes
- Chart of Accounts is read-only.
Importing the Items
- QBO Items usually are broad
- Inventory Items
- The Problem
- The Solution
- Refactor Import Code
- Additional advantages
- When To Use
One Off Importing
- Manually kicking off an import
- What’s Next?
The Leanpub 45-day 100% Happiness Guarantee
Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms...