GET /api/apps/{AppID}/versions
Returns a list of versions for the specified app.
Authorization Roles/Permissions: App team member, Business Admin, Site Admin, or other authorized user
This topic includes the following sections:
HTTP Method
GET
URL
https://{hostname}/api/apps/{AppID}/versions
Sample Request
The example below gets the versions for a specific app.
Sample request URL
https://{hostname}/api/apps/app10033.acmepaymentscorp/versions
Sample request headers
Accept: application/json, text/javascript, */*; q=0.01 Host:{hostname} X-Csrf-Token_acmepaymentscorp: TokenID%3D8ed70a13-8469-11e8-b37a-b155e4eabeb8%2CexpirationTime%3D153...
Sample request body
Not applicable.
Request Headers
For general information on request header values, refer to HTTP Request Headers.
Header | Description |
---|---|
Accept |
application/xml, text/xml, application/json application/vnd.soa.v71+json, application/vnd.soa.v71+xml application/vnd.soa.v72+json, application/vnd.soa.v72+xml application/vnd.soa.v80+json, application/vnd.soa.v80+xml application/vnd.soa.v81+json, application/vnd.soa.v81+xml |
Cookie | AtmoAuthToken_{fedmemberid}={cookie value, which usually starts with TokenID}—The platform cookie. This is the Akana API Platform authorization token, and must be sent with every API request that requires login. For more information and an example, see Session cookies. |
X-Csrf-Token_{fedmemberID} | The CSRF prevention header; may or may not be required, depending on platform settings. See CSRF Prevention on the Platform. By default, the CSRF header is not required for GET operations and is required for all others, with a few exceptions relating to user login. |
Request Parameters
Parameter | Parm Type | Data Type | Required | Description |
---|---|---|---|---|
AppID | Path | string | Yes | The unique ID for a specific app. |
Response
If successful, this operation returns HTTP status code 200, with information about the app versions in JSON or XML format.
Sample Response
In the example below, the app has only one version.
Sample response headers
HTTP/1.1 200 OK Date: Tue, 24 Jul 2012 21:00:56 GMT Content-Type: application/json
Sample response body
{ "channel" : { "title" : "Application versions", "item" : [ { "title" : "1.0", "description" : "Multi-player card game for Android phones.", "category" : [ { "value" : "app-version", "domain" : "uddi:soa.com:resourcetype" }, { "value" : "Sandbox", "domain" : "uddi:soa.com:environment" }, { "value" : "com.soa.app.state.sandbox", "domain" : "uddi:soa.com:application.state" }, { "value" : "cards", "domain" : "uddi:soa.com:tag" }, { "value" : "game", "domain" : "uddi:soa.com:tag" } ], "guid" : { "value" : "2FEBF9WSXVa5qHCVSnue41AV.acmepaymentscorp" }, "pubDate" : "Tue, 24 Jul 2012 13:45:12 PDT", "EntityReferences" : { "EntityReference" : [ { "Title" : "110", "Guid" : "app10033.acmepaymentscorp", "Category" : [ { "value" : "app", "domain" : "uddi:soa.com:resourcetype" } ] } ] } } ] }, "version" : "1.0" }
Response Headers
For general information on response header values, refer to HTTP Response Headers.
Header | Description |
---|---|
Content-Type |
application/xml, text/xml, application/json application/vnd.soa.v71+json, application/vnd.soa.v71+xml application/vnd.soa.v72+json, application/vnd.soa.v72+xml application/vnd.soa.v80+json, application/vnd.soa.v80+xml application/vnd.soa.v81+json, application/vnd.soa.v81+xml |
Response Body
The response body is in the form of an RSS channel, and includes the items listed below. The RSS version is 1.0. The title of the RSS channel is Application versions. Each item in the channel represents one app version, and includes the information listed below.
Name | Description |
---|---|
title | Version number. |
description | Description of the app version. |
category[ ] |
An array of sets of two name/value pairs, each including Value and Domain, with a value for each. A category for the "uddi:soa.com:resourcetype" domain is provided with the value "App Version". A second category for the "uddi:soa.com:tag" domain is provided for each tag assigned to the app version. A third category for the "uddi:soa.com:application.state" domain is provided with the value representing the version's state. There is also a name/value pair for each tag assigned to the app version. For information regarding app state, refer to Determining the State Value of an App. |
guid | App version ID. |
pubDate | A date/time stamp identifying when the app version was last updated. |
EntityReference | Reference to the app for which versions are being retrieved: Title, which is the app name, GUID, the unique AppID, and Category indicating the resource type is app. |
Error Codes/Messages
If the call is unsuccessful an error code/message is returned. One or more examples of possible errors for this operation are shown below.
Item | Value |
---|---|
401 | Unauthorized. For example, you would get this response if you didn't include the custom X-Csrf-Token_{fedmemberID} header in the request, when it was required by the platform settings; or if you included an invalid or expired value for this header. You would also get this response for any operation that requires login (almost all) if the login cookie was missing. |
404 | The resource could not be found. |
500 | An error occurred processing the call. |
More information about Akana API Platform API error messages.