Quickbooks SDK

Why the official SDK is terrible

• Completely unresponsive to community issues and PRs
• Uses a complex soup of autogenerated classes and slow XML API
• Bad type documentation sabatoges static analysis: https://github.com/intuit/QuickBooks-V3-PHP-SDK/issues/425
• EntityType is impossible to read from any objects:
  • https://github.com/intuit/QuickBooks-V3-PHP-SDK/issues/38
  • https://github.com/intuit/QuickBooks-V3-PHP-SDK/issues/336

Projects to track

• Mature, well-maintained Laravel service adapter, but oriented around user-level tokens and wrapping the official SDK: https://github.com/spinen/laravel-quickbooks-client
• From-scratch SDK with minimal deps that uses JSON API directly, but does contain a bunch of type-specific wrappers/builders: https://github.com/rangka/quickbooks

Roadmap

We want to eventually migrate to an SDK based on making JSON REST calls that does not rely on the official SDK. rangka/quickbooks looks like a really good candidate. Ideally we migrate to using it across the board and completely remove the official SDK from our project.

Jarvus can make a v3 release of our laravel-quickbooks adapter that migrates fully to it, and we can fork of maintenence of the v2 release line.