What is returned from Data Service

Hi Innovators!

This is the first of many other videos where we will be showing how you can access and make the best use of the Nimbus data services to help you with your innovations.
In this video, we will show you how you can make a query to the Nimbus data service and what results you will be getting.

Video Highlights

• Accessing Data Service via a Web Browser
  -  format: [DATA SERVICE URI]+[Data Set Name]+[AuthenticationDetails(AccountKey & UniqueUserID)]+[Filters (Optional) ]
  - Authentication will be placed into the ‘Request Header’ instead of the QueryString in Release 1 of Project Nimbus.
  - Authentication comprises of the ‘AccountKey’ which is similar to an API Key and a ‘UniqueUserID’ which is just a GUID.
  - Authentication is needed for metering/billing
• Content Returned
  - Default content is an Atom Feed.
  - If ‘Accept’ in your request header is set to “application/json” a JSON formatted string will be returned to the client. 

Hi everyone! Really hope you found the video useful.

Here are some of the links you can try in your browser to test the services.

http://nimbusproject.cloudapp.net/neaodataservice.svc/ForecastSet?AccountKey=NimbusAdmin&UniqueUserID=A66D951F49F54A63B040CFAA2FD553C0

http://nimbusproject.cloudapp.net/neaodataservice.svc/NowcastSet?AccountKey=NimbusAdmin&UniqueUserID=A66D951F49F54A63B040CFAA2FD553C0

Please take note that the authentication details “AccountKey” & “UniqueUserID” is now appended in the URI as QueryString parameters. In Release 1, you will have to put these authentication details in the Request Header instead. A little more information about ’AccountKey’ and ‘UniqueUserID’: http://projectnimbus.org/2010/03/03/authentication-information-in-the-request-header/