Can anyone share creative ways of using the API Key's...

[Anon Anon]

Can anyone share creative ways of using the API Key's (available from the Application Manager page)?  Just looking for ideas from the community.   Thanks! https://help.rallydev.com/rally-application-manager

[Anon Anon]

I had requested additional documentation, but I am hoping to have mare complex integrations of Rally data outside of the application. i.e. reporting, pivots

[Anon Anon]

Nice.  Share when you found something?  Sounds very useful.

[Anon Anon]

Here is what I received from Rally support -------------------------------------------------------------- Thanks for contacting Rally Support. The API Key that you configure via the Rally Application Manager: https://rally1.rallydev.com/login May be utilized as a valid authentication token. To use one, you can make calls to Rally with a cookie or header called ZSESSIONID set to the secret_key value of your API key. For example: Cookie: ZSESSIONID=_ffQI6qxyQmOwyzyEcY65zy3ylAAS0fVhtuKAr6xEGk; You can delete or regenerate an existing API Key to revoke access to keys you have previously issued.and is passed to the server as a ZSESSIONID Cookie in the HTTP Request headers: There are some code samples/examples of this utilization for Clojure, Ruby, and Python, located here: https://github.com/RallySoftware/rally-oauth-examples In these samples, the value of the secret_key comes from an interactive OAuth authentication request, however, the usage in terms of how it is passed back to the server via the ZSESSIONID cookie, is the same. Several of Rally's REST toolkits: https://github.com/RallyTools/RallyRestToolkitForRuby https://github.com/RallyTools/rally-node Have support for use of the API key built in. API Key for Rally's other REST toolkits such as Java and .NET should happen soon, although I can't make any promises on timing. ------------------------------------------------------------ Hope this is useful

[Anon Anon]

Totally.  Thank you, David!

[karimm]

One way is to call the Rally API to get data into Excel and do complex transformations.
This was has many benefits of the Excel Add-In because it allows for more complex automation.
This is a video I made about it: https://www.youtube.com/watch?v=5GEHkXyt8OM

[Inna Shulman]

Hi, 
I've made a full scale integration between two workspaces of our subscription: separate otherwise, all cross-updates go via 3rd-party "integration" engine, http calls all the way.
And I have made a couple of PowerBI report files pulling data from Rally and presenting several reports each.
I also generate a periodic report, emailed to predefined audience.

Our QA teams made a number of email reports that pull data from Rally and send targeted emails to defect owners.
Another integration was made with the test running lab software: they pull the test plan from Rally and then update the test status after the run, while doing and logging all kind of stuff in that external application.

Finally, I'm adding process shaping to mandate certain fields based on the work item schedule state, for example.

Basically this API capability is what makes Rally viable in our setting as it allows to cover for most of the missing features. Not the optimal solution in any way, but so far it is been cost effective. Hats off to Sagi and the rest of the original support team that helped with initial struggles. Once you master the basics, it is pretty smooth from there.

[Inna Shulman]

Ha, just noticed the original post was from 2014 :). Not sure what was available back then. My experience is from last 2-3 years. Hope it would be helpful to others.