I was previously using QBO/QBD API to connect to quickbooks enterprise, but it looks like these services have been deprecated.
The new QB API V3 seems to only work with quickbooks online.
For example, when I navigate to API explorer for my customer's enterprise data, I receive the message:
You're logged in with an account that does not have a QuickBooks Online subscription. Please try another account.
Do we continue to use the old API to access enterprise data?
For QBD, you can use QBSDK. If you have a published app which uses V2 then it is recommended to make it use V3.
For QBO, you can always use V3 REST APIs.
Thanks
Related
My Client wants to send his eCommerce data to QuickBooks, I checked that we can use QuickBooks PHP SDK, to send data to QuickBooks: https://github.com/intuit/QuickBooks-V3-PHP-SDK.
But my client using QuickBooks desktop.
My question is can I use the same SDK to sync data to QuickBooks desktop?
can i use the same SDK to sync data to QuickBooks desktop?
No. If you read the notes on that page, it says it's for QuickBooks Online, which you're not using (emphasis mine):
PHP client for connecting to the ****QuickBooks Online**** V3 REST API.
But you can use this one instead:
https://github.com/consolibyte/quickbooks-php
Specifically, you may want to follow the quick-start:
http://www.consolibyte.com/docs/index.php/PHP_DevKit_for_QuickBooks_-_Quick-Start
Which walks you through using the QuickBooks Web Connector, which Intuit also documents thoroughly over here:
https://developer.intuit.com/app/developer/qbdesktop/docs/get-started
I am integrating Onenote with my application. I am using MS Graph API's for getting data from Onenote. To consume the api's I am generating the token as mentioned at link get auth tokens.
I am registering my application at MS application registration portal. Do we need to purchase any kind of paid license to use services provided by MS graph API's.
The app registration process seems simple and doesn't differentiate between applications that can be used in production/test environment.
The app registration process seems simple and doesn't differentiate
between applications that can be used in production/test environment.
Apps registered in the app registration portal can be used for production or test environments. There isn't any switch that needs to be set when you're ready to ship. Congrats on shipping your app to production!
Do we need to purchase any kind of paid license to use services
provided by MS graph API's.
We don't charge for access to the API. Some of the services exposed in Graph via APIs require licenses like Intune. It sounds like you're using OneNote so as long as users of your app are already using OneNote you're fine to access their notes via our API. Just be sure not to DDOS us :)
If you can share, our community would love to hear about your app!
1.How to programmatically connect with QuickBooks Online using .NET? We followed the below article but this needs manual intervention to connect.
http://ippdocs.intuit.com/0025_QuickBooksAPI/0010_Getting_Started/0020_Connect/0010_From_Within_Your_App/Test_the_In-App_Connect_Flow
Initially we developed the sample application using the code:
https://github.com/IntuitDeveloperRelations/IPP_Sample_Code/tree/master/QuickbooksAPI/DotNet/WebForms%20application
2.Which type of integration method we have to use Json or .NET SDK library? Most of the Json examples are code fragment only, Where we can download the sample application using Json with .NET
You cannot connect to Quickbooks APIs without manual intervention as it is a part of the 3 legged OAUTH flow.
The .Net SDK supports XML and JSON. There is no separate JSON library. The sample app for Dotnet in v3 is not yet available. Please refer to the docs for generating the JSON requests.
https://developer.intuit.com
If you want to create SaaS application and want to publish it in Appcenter then you need to implement OAuth flow which needs user's input for authorization. In the dev env, using the above sample app, you can get the OAuth tokens(consumer key, consumer secret, access key and access token) which you can use in your app to call all API endpoints.
https://developer.intuit.com/docs/0025_quickbooksapi/0055_devkits/0150_ipp_.net_devkit_3.0/0002_synchronous_calls/0001_data_service_apis#Step_3:_Build_the_ServiceContext
FAQ - https://developer.intuit.com/docs/0025_quickbooksapi/0058_faq
.Net V3 Link - https://developer.intuit.com/docs/0025_quickbooksapi/0055_devkits/0150_ipp_.net_devkit_3.0
But Intuit Quickbooks API(V2/V3) are only for SaaS app. If you want to create some custom solution for one company then you should use QBSDK.
Ref -https://developer.intuit.com/docs/0025_quickbooksapi/0055_devkits/0250_qb
Thanks
I'm doing custom QB development for a accounting firm and the question I have is has Intuit announced its decision regarding its chosen, supported API or SDK for QB Desktop and QB online?
Perhaps i've missed something, but it appears from reviewing the code samples in the Windows Azure SDK FOR Quickbooks and comparing them to the IPP API, that there are differences between what one can do with each approach, but neither one seems capable of doing everything the other does. is the presumption that the SDK is targeting the QB desktop platform and the IPP V3 targetS THE QB Online platform incorrect?
Intuit has 3 separate sets of APIs right now, 2 of which are generally available:
the QuickBooks SDK (available for general use)
IPP, v2 data services (available for general use) IPP
v3 data services (available for private BETA ONLY - you need to get approval from Intuit)
The QuickBooks SDK can be used to access both QuickBooks Online, and QuickBooks desktop. The QuickBooks Online APIs are somewhat weak, and will likely be deprecated in the future.
IPP v2 data services can be used to access both QuickBooks Online, and QuickBooks desktop. The IPP APIs are available only to SaaS services (e.g. you are charging your customers a recurring fee to connect their QuickBooks to your app).
IPP v3 data services can be used to access both QuickBooks Online, and QuickBooks desktop, but are currently in BETA and you need permission from Intuit to use them. The IPP APIs are also available only to SaaS services (e.g. you are charging your customers a recurring fee to connect their QuickBooks to your app).
The Windows Azure samples (and the other DevKits) are used to access IPP v2 or v3 data services (e.g. they are not a separate API, they are a code library wrapped around the IPP APIs).
As far as this goes:
is the presumption that the SDK is targeting the QB desktop platform
and the IPP V3 targetS THE QB Online platform incorrect?
Both the SDK and IPP target both QuickBooks Online and QuickBooks desktop.
I have a web-based application, which integrates with QuickBooks through the QuickBooks Web Connector. This works great for desktop versions of QuickBooks. However, I'm looking to add support for QuickBooks Online, and the Web Connector can't be used with QuickBooks Online.
How do I integrate my application with QuickBooks Online? If possible, I'd like to use the web service that is already working with the Web Connector.
Please visit http://developer.intuit.com and click on the Integrate your app with QuickBooks link in the Intuit Partner Platform section. The link brings up our QuickBooks API documentation. You should focus on the V2 API if you want something that will be ready to use now. The V3 API will be released publically later this year and will allow you to integrate your application with the Global version of QuickBooks Online.
Register as a developer and if you have any further questions you can submit a support ticket and we'll get back to you.