In a recent email from Intuit we seen in the migration pages that the QuickBooks online
To:
developers currently using the QuickBooks Online SDK (aka QBO XML SDK (SOAP)) to access QuickBooks Online company data.
and
migrating QuickBooks Online SDK to QuickBooks Online REST API v3 .
on
https://developer.intuit.com/blog/2013/12/19/2014-roadmap-and-migration-dates-for-existing-developers
and
https://developer.intuit.com/docs/0025_quickbooksapi/0058_faq/qbo_xml_sdk_%28soap%29_to_v3_rest_migration
Does this apply to the QBSDK12,11, etc. that support QBO.
If you're using qbXML to communicate with QuickBooks Online, then it applies.
This includes ANY and ALL QuickBooks SDK applications that communicate with QuickBooks Online. The entire SDK is qbXML based, so any SDK apps that deal with QuickBooks Online need to be ported to the new REST v3 API.
Does this apply to the QBSDK12,11, etc. that support QBO.
Yes.
Related
I am looking for a complete online reference for iManage's latest API. On googling, can see references to iManage v2 documentation, but that seems to be bit old and where can I find latest API if at all there is one
The latest version which is constantly updated is available at https://help.imanage.com/hc/en-us/sections/360000214214-iManage-Work-REST-API-Documentation - you'll need a login to IManage's support site to access this though. If you don't have credentials you can raise a ticket with your support provider to get access.
If you have an on premises server that's licenced for the API, you'll find the documentation for that specific version at https://YOURSERVERNAME/api-docs/
iManage has 3 different versions of API's
COM API > This is a legacy classic api which is reaching EOL on Dec 2023. So it is not recommended any more.
REST API v1.0 > EOL already reached (Dec 2022)
If you're on-prem technically you can use REST API 1.0 till iManage Work 10.4.4 (but please validate) but you will not have any support from iManage in case of any issues
REST API 2.0 (also called iManage Universal API)
This is the latest version and going forward you need to use this version. And if I am not wrong this is supported from iManage Work 10.2.3.
You can find latest documentation at iManage Universal API 2.0
Or you can find your Work server specific documentation https://YOURSERVERNAME/api-docs/ (Provided you entered API license while installing iManage Work software)
I searched for the One Drive scripting language, but found only this (Live SDK API): https://msdn.microsoft.com/en-us/library/windows/apps/hh826521.aspx?f=255&MSPPError=-2147217396
This shares similarities more like a Google Drive API. Does Microsoft OneDrive have web based scripting possibility similar to Google Apps Script?
About how to call the Live SDK APIs: the JavaScript API (Windows Store apps and web), the Managed API (Windows Runtime apps), the iOS API, and the Android API . You may want the JavaScript API , please click here for how to use the Live SDK JavaScript API in your web app.
As I have understand - Live SDK has supporting 2 main features:
OneDrive and Microsoft account
Now with release OneDrive SDK all OneDrive features are coud be found in it.
But if you want to access Microsoft Account you still can use only Live SDK.
Seems that now we have 2 branches - Live SDK and OneDrive SDK.
One for account and another for files.
I am asking because sometimes it's not clearly written and looks like live SDk is depricated.
They are deprecated according to this:
The Live Connect APIs are deprecated. We recommend that you use the
Outlook REST APIs to build your solutions. This will extend your reach
to Outlook.com users and Office 365 enterprise customers. Although the
Live Connect APIs will be supported in Outlook.com for the short term,
existing Live Connect API solutions might stop working without
advanced notice. If your app is using IMAP with OAuth 2.0, it will
continue to work, but our REST APIs are the primary APIs for building
apps that connect to Outlook.com and Office 365. Read the article on
how you can take advantage of the Outlook REST APIs.
https://msdn.microsoft.com/en-us/library/hh243641.aspx
I need some guidelines here. I am creating an online booking system for my client that interfaces with QuickBooks on their internal network (desktop QuickBooks, not online).
Do I need to go the full "publish app" route? I do not wish to sell this app in the marketplace. This is merely a custom booking system designed and paid for by the client. It seems like I need to "publish" the app in the marketplace for them to be able to use it.
Are there ways around this?
Update 06/23/2015 - To connect to a desktop QuickBooks installation the SDK with the Web Connector is now the only recommended approach. Intuit is removing Intuit Partner Platform (IPP) integration to desktop QuickBooks.
For the SDK/Web Connector, you don't need to go through any publication process or anything like that. Just build the solution, and connector your client.
There's a pretty good overview of how the QuickBooks web connector works on our QuickBooks wiki.
The QuickBooks SDK download also includes a huge PDF with detailed documentation about how to implement SDK/Web Connector applications as well.
Our company uses Quickbooks Online to track our books. When our application bills a customer, it would be nice to have that information recorded automatically in QB rather than logging in to QB Online to fill in the info.
Is there a way to accomplish this using Quickbook's APIs? The Intuit developer information is very confusing; it is mainly oriented towards extending the desktop version of Quickbooks or developing apps to publish in Intuit's app store.
Have you successfully created a web or other service-side app that was able to pull data to or from QB Online?
If you're building a one-off application, the QuickBooks Online qbXML gateway is the way to go. It's a pretty simple POST-your-XML-requests-over-HTTP sort of interface that gives you access to a large chunk (but not all) of the functionality within QuickBooks Online.
If you're building a SaaS application, then you should be looking at the Intuit Partner Platform instead. It sounds like you're building a one-off app for your company, so we'll focus on that:
If you look on my QuickBooks integration wiki there are some example qbXML requests to show you how to sign on, and how to POST qbXML requests to the QuickBooks servers.
You don't specify a language, but if you're using PHP, then try out my open-source QuickBooks PHP DevKit (look at docs/example_online_edition.php and docs/example_raw_online_edition.php in the .zip nightly builds).
You'll want to use the QuickBooks OSR for qbXML reference. The QuickBooks SDK also has 40+ pages specifically about QuickBooks Online Edition that you should probably review.
The Intuit Developer Forums are another good resource.