1
HP
Gloe API v1
hpgloe.comIn this document we describe the
HP
Gloe service API. The goal of this document is topromote mashup services and customized clients to be written on top of Gloe and toallow syndication of Gloe content. The API also allows native clients to be built forplatforms that Gloe currently does not support. For a general description of Gloe see theseparate
An Overview of HP Gloe
document.
General Protocol
All APIs support JSONP, that is a
callback
HTTP GET parameter may be passed and theresult is then the string
callback
(
json data
);All operations may be called using HTTP GET with the format:
http://
www.hpgloe.com
/json/
operation
/?
param1
=
val1
&
param2
=
val2
…
Authentication
Most operations can be called without requiring authentication. There are two ways of authenticating a user, with Facebook Connect, and with the native Gloe authenticationprotocol.To initiate a Facebook Connect login a browser should be opened with the URL:http://
www.hpgloe.com
/json/
mobilefblogin
/ This will direct the user to the Facebook login page and set the cookies in the browserthat are required to link the users’ Facebook account with a corresponding Gloe account.For first time logins a new Gloe account will be created dynamically/ For more information about Facebook connect see
http://developers.facebook.com/connect.php
To login to a native Gloe account (without requiring a Facebook identity) the user mustfirst register an account using the register operation (see below) to obtain a Gloe
nickname
and
recommendation key
. Authenticated requests must contain a
timestamp
parameter with the current time using the time format
%Y%m%d%H%M%S,
e.g. 20091231235959. The request must also contain a
user
parameter with the
nickname
of a registered Gloe user. The parameter values must then be signed in alphabetical orderusing the HMAC/SHA1 algorithm (See e.g., the Authentication section in
http://docs.amazonwebservices.com/AWSEC2/latest/DeveloperGuide/index.html?using-query-api.html
for implementationdetails) with the
recommendation key
. Note Gloe uses the AWS signature version 1scheme. The difference to v2 are: we don't include the parameter names in the data tosign, we order by parameter name alphabetically, and we only support SHA1. The
Leave a Comment