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.
Related
I've written a small application which accesses the REST API of Atlassian Bamboo.
As the documentation describes:
To get the latest version of the API, you can also use the latest key-word.
So I used the latest keyword to access the version. But I noticed now, after migrating to the new Bamboo version, that this wasn't the best solution, because the new version seems to have changed some things in the API and breaks my application.
Now I would like to build my application with a specific API version. But how can I tell: which is the exact version of the current API?
The only thing which the documentation is saying about this:
The API version is independent of the Bamboo release number.
The API version may, or may not, change with a new Bamboo release. The API version number will change only when the updates to the API break the API contract, requiring changes in the code which uses the API. ...
The documentation of the single Bamboo versions (like the one for 6.6.2) only uses the latest keyword as reference.
And even the REST api itself (under /rest/api/latest/info) only tells me the Bamboo version, not the API version:
<info>
<version>6.6.2</version>
<edition/>
<buildDate>2018-08-14T09:01:47.000+02:00</buildDate>
<buildNumber>60606</buildNumber>
<state>RUNNING</state>
</info>
So how do I find the exact API version of my Bamboo installation?
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
Due to some issues I'm having with Protractor 5, I am currently using Protractor 4.0.14. I need to get the API documentation for the exact version of Protractor I am using.
Best I understand, the API documentation at the enter link description here reflects the latest version.
What should I do in order to obtain the API docs for the exact version I am using?
You can do it with the following steps
Checkout the protractor repo and switch to the protractor 4.0.14 tag
Read the documentation about how to generate the website here
You will now have the 4.0.14 version on your local machine
Protractor API v.1.1.1 was on the official GitHub till Nov 2, 2014. After it date protractor API was removed and pointed to the website without availability to change version of API. I have found just a changelog with a list of API versions.
How to install rest api on open-fire server version 3.9?
we have a pre implemented application on open-fire 3.9. Now we want to update the functionality with rest api. But rest api required open-fire version 4.0+.
So how is it possible?
if any one have an alternate then please help me.
You need an older version of the plugin, hoping it supports what you need.
You can download by following this link:
https://community.igniterealtime.org/thread/56342
I will try to make it simplify. I am using windows azure cloud to host our web services and databases. and these web services are accessible via URL: "https://server.mydomain.com"
now we made a few major changes to our model and hence web services as a whole. This breaks the API interface for older users. Now we want to deploy the latest version on URL: "https://server.mydomain.com/v2" so that old users can still access the older version.
I searched around SO and other resources but i couldnt find a definite answer how to deploy new version without messing up the old version.
Anything in right direction will be helpful.
In one of the projects I was working on, we built in a versioning scheme on top of our Web API. We used this tutorial to get started. I would recommend starting there.
Sorry for the generic answer, if you post some more specifics I will make some updates.
I'd suggest to deploy separate cloud service and use "v2.server.mydomain.com"