We are planning to upgrade our app from V2 to V3. I have read all the documents but there is nothing specific saying the issues of moving V2 to V3. V3 is REST based and V2 was based on QBXML so anything specific you want developers to note for upgrading the code to support V3? Also any upgrade tool would be awesome that can replace V2 to V3 would be very helpful to developers.
You can refer the following docs -
https://developer.intuit.com/docs/0025_quickbooksapi
https://developer.intuit.com/docs/#api/deki/files/1463/gettingstartedwithquickbooks.pdf
JAVA/C#/PHP devkits and usage details are available here -
https://developer.intuit.com/docs/0025_quickbooksapi/0055_devkits
PN - V2 and V3 both are REST based APIs.
If you have any entity specific qts then you can post it in IPP's live community.
https://intuitpartnerplatform.lc.intuit.com/
Thanks
Related
Is there any workaround for using the new version (V2) of Dialogflow API in Unity? There used to be a SDK for the previous version but apparently it will be discontinued next year...
Since there is no official Dialogflow-Unity-SDK, you can use the Google.Api.Dialogflow.v2 library.
Details at
Authenticating Request with Google.Apis.DialogFlow.V2
Note: Remember that you can't use your token anymore. You need to create a credential file: Details at: https://medium.com/#tzahi/how-to-setup-dialogflow-v2-authentication-programmatically-with-node-js-b37fa4815d89
we have TFS 2018 and are able to call the following URL using PAT for authorization:
https://our.tfs/tfs/Our.Project.Collection/Our Team Project/_apis/wit/workitems?ids=1234&?api-version=2.0
This quite basic call returns expected results.
Trying to request API calls from the following documentation results always in 404 Page not found:
https://learn.microsoft.com/de-de/rest/api/vsts/work/backlogs/list?view=vsts-rest-4.1
For example:
https://our.tfs/tfs/Our.ProjectCollection/Our Team Project/_apis/work/backlogs?api-version=4.1
which yields the mentioned 404 error.
According Microsoft, the API is supported in version 4.0 on TFS 2018:
https://learn.microsoft.com/en-us/vsts/integrate/concepts/rest-api-versioning?view=tfs-2018
However, it seems calling the API in version 4.1 in the way the documentation describes it here only works for VSTS but not for TFS
Do I understand it correctly that any API calls to API version greater than 4.0 are currently only supported by VSTS but not on TFS on prem?
This would mean we have to live with API calls documented in the "Previous REST API Versions" when using TFS 2018 on prem?
The REST API format you used is incorrect, you missed the Team parameter
The format should be:
GET http://tfs2018:8080/tfs/DefaultCollection/{Project}/{Team}/_apis/work/backlogs?api-version=4.1-preview.1
It works without any issue on my side.
I believe you will get something by taking a look at these links, see
Visual Studio Team Services REST API Reference
REST API Overview for Visual Studio Team Services and Team Foundation Server
I was able to follow this example:
https://{instance}[/{collection}[/{team-project}]/_apis[/{area}]/{resource}?api-version={version}
see what Microsoft speaks about version 4.1 of this doc.
APIs e uso REST comuns
Discussion on TFS MS Apis
Similar discussion
Hugs
I've wanted to get the vmware-tags from vSphere 5.5 using pyvmomi 5.5 - which is not possible because of limitations in the vSphere 5.5 Python API.
But now when we've upgraded vSphere to 6.0 - is it possible to get the tags somehow?
This will provide the python bindings using pyvmomi for the tagging api
http://developercenter.vmware.com/web/sdk/60/vcloudsuite-python
For those who still looking for recipe in 2021 with vsphere 6.5+, you may obtain tags using REST API or vSphere Automation SDK.
You can find full examples here (for the REST API) and in my answer here (for the SDK)
I'm wondering if the Azure Notification Hubs REST API documentation is still correct and up-to-date or if there is already a newer API version than "2013-08" that can be used.
All the single pages show "Updated: February 26, 2015", but I guess it was just a meta data update of all the pages, since the API version didn't change, it's still "2013-08".
Here (and here) is an example for the REST API usage from Elio Damaggio which uses "2013-10" as the api version.
I tried all possible api version values in the format "yyyy-mm" from "2013-10" to "2015-03" and the following were working: "2013-10", "2014-01", "2014-05", "2014-08", "2014-09", "2015-01".
Does anyone use a newer API version than "2013-08" or does anyone know anything about a newer API version or documentation? Specifically, does anyone know if there is a documentation for a newer API version, e.g. "2015-01", or at least a changelog?
Got an answer on MSDN forums:
The latest version is 2015-01. All or most of features works with
starting version 2013-08.
Version in documentation indicates that minimum version required for
working that feature. Hence, all documentation is pointing to 2013-08.
...
Yes, you can use version 2015-01 instead of 2013-08. There won’t be
any difference because we didn’t do any breaking changes from 2013-08.
All the features works from version 2013-08.
Moreover, the source code for the Java REST wrapper for Windows Azure Notification Hubs on github seems to be a good reference. It is using api version "2014-09", not "2015-01" right now, but at least it includes the registration code for Amazon Device Messaging and Baidu Cloud Push which are currently missing in the REST API documentation.
There are some entities that are supported in V2 that are not yet supported in V3. Is there any guidance on how to use both V2 and V3 in the same app?
A hybrid model for v2 and v3 is not supported as the assembly names might conflict in the same project. You can use 2 different projects in same namespace to access v2 and v3 separately.