Intuit is delighted to increase its support for the GraphQL community by becoming a founding member of the GraphQL Foundation. Third-party time tracking and benefits suppliers can connect directly to QuickBooks Online using the Intuit QuickBooks Online Payroll GraphQL.
QuickBooks offers a mechanism to supply deductions, pensions, benefits, synchronize employee contributions, and more. It has capabilities for tracking benefits, time, and other things. With the help of platform APIs, Intuit offers services like TurboTax, QuickBooks, and Mint that enable developers to create software for small business accounting ecosystems.
For more than 18 years ago. Intuit realised that small business owners using QuickBooks were also utilising other programmes. To assist them to run their operations, which was exacerbating the pain of having to enter data twice for their customers. In order to meet this challenge, we released the first QuickBooks Desktop API in the first quarter of 2001. Subsequently, a community of several hundred business applications that linked with QuickBooks quickly grew.
On April 12 and 13, 2019. Rajat Khare had the incredible honour of speaking at the inaugural GraphQL Asia Conference in Bangalore. Intuit began using GraphQL services in 2015. He has had the chance to work on numerous projects that create GraphQL-based experiences and services. His experiences with GraphQL and how Intuit’s QuickBooks product has embraced GraphQL at scale. The same was shared in great detail at GraphQL Asia. At GraphQL Asia 2019, Rajat Khare highlighted in a video, the lessons he learned from working with GraphQL.
As a GraphQL adopter, there was a great deal of internal worry about whether this new technology will be widely accepted or not. To be safe, Intuit created a multi-protocol strategy for their API, putting a complete emphasis on the system’s nouns. Despite some setbacks along the way, Intuit has reaped major benefits from its adoption of GraphQL, which began in 2015 with SBSEG and has since spread to other Intuit business units. We anticipate making even more progress when we correct our course, start utilising the contributions of the larger GraphQL community, and give back to the community our own innovations created to support huge schemas.