AppInfo

The AppInfo API lets you request information such as name, version, apiKey, platform, and creation date of one or all of your company’s applications.

Making a Request

Requests should be of the form:

http://api.flurry.com/appInfo/FUNCTION_NAME?apiAccessCode=APIACCESSCODE&apiKey=APIKEY

Where the FUNCTION_NAME is one of the following:

  • getApplication - Information on a specific project.
  • getAllApplications - Information on all projects under a specific company.

APIACCESSCODE is the unique code given to you to access Flurry APIs. This can be found by logging into the Flurry website and by going to the “manage” link at the top center of the page.

APIKEY is the unique code for each application. This can be found by logging into the Flurry website, then by going to the link “Manage Applications” and finally by selecting the application desired.

Response Format

Flurry APIs current support two output formats: XML and JSON.

The format of the response data depends on the value of the Accept header you send in the HTTP request.

If you specify “application/xml” when calling getApplication, you receive an XML-formatted response similar to the following:

<appInfo name="Project Name" version="1.0" generatedDate="3/1/10 2:10 PM" createdDate="2010-03-01" platform="Platform" category="Category">      <version name="1.0" createdDate="2010-03-01" />
     <version name="2.0" createdDate="2010-03-02" />
     ...
</appInfo>

If you specify “application/json” you will receive a JSON-formatted response similar to the following.

{"@name":"Project Name",
 "@version":"1.0",
 "@generatedDate":"3/1/10 2:10 PM",
 "@createdDate":"2010-03-01",
 "@platform":"Platform",
 "version":[
   {
     "@name":"1.0",
     "@createdDate":"2010-03-01"
   },
   {
     "@name":"2.0",
     "@createdDate":"2010-03-02"
   },
   ...
   ]
}

In the above response, please note that the top-level @version is the API response version, and not the version name of your app. The app versions are listed in the version array.

If you specify “application/xml” when calling getAllApplications, you receive an XML-formatted response similar to the following:

<appInfo name="Project Name" version="1.0" generatedDate="3/1/10 2:10 PM" createdDate="2010-03-01" platform="Platform" category="Category">      <version name="1.0" createdDate="2010-03-01" />
     <version name="2.0" createdDate="2010-03-02" />
     ...
</appInfo>

If you specify “application/json” when calling getAllApplications, you receive a JSON-formatted response similar to the following.

{"@companyName":"Company Name",
 "@version":"1.0",
 "@generatedDate":"3/1/10 2:10 PM",
 "application":[
    {
      "@name":"Application #1 name",
      "@apiKey":"1234",
      "@createdDate":"2010-03-01"
      "@platform": "Platform name"},
    {
      "@name":"Application #2 name",
      "@apiKey":"4321"
    },
     ...
    ]
}

Error codes

If something is wrong with the request or if there is a system problem, you will receive an error response instead of the expected response. This is signified by an HTTP response code other than 200 (OK) and is accompanied by content similar to the following:

<appInfo name="Project Name" version="1.0" generatedDate="3/1/10 2:10 PM" createdDate="2010-03-01" platform="Platform" category="Category">      <version name="1.0" createdDate="2010-03-01" />
     <version name="2.0" createdDate="2010-03-02" />
     ...
</appInfo>

If you receive one of these errors and are unable to determine the cause from the message provided, please contact Flurry support (support@flurry.com) along with the error code you receive.

In some cases, a system error will occur that prevents even an error message from being returned. In these cases, you will receive a 500 server failure response code.