Identities API

This Identities API creates a list of found identities and associated service endpoints for a given individual. It uses Ident Engine library to wrap Google’s Social Graph API, returning a much richer result set than using Google’s API directly. It is taking advantage of YQL opentable to host the core of the Ident Engine's JavaScript.

Try it out...

Profile URL 

Use inward edges

End points

Icon Path 

Format: XML JSON

Example

I have created an example which demostrates the use of this API.

API parameters

The parameters "urls", "useInwardEdges", "endPoints" and "iconPath" are used to create the YQL query parameter "q" i.e.

use "http://identengine.com/opentables/identities.xml"; select * from identities where urls="http://twitter.com/glennjones" and useInwardEdges=1 and  endPoints=1 and iconPath="http://identengine/identi/icons/";

urls

A single URL or a comma delimited list of URLs of profiles

useInwardEdges

Use inward edges, this maps direclty to the Google Social Graph API "edi" query parameter. Setting this to 1 will return more results, but incease the chance of errors.

endPoints

Switches on or off the inclusion of service end point data.

iconPath

The path to add to the front of the icon name.

format

The YQL output format xml or json.

diagnostics

Switches on or off the YQL diagnostics information.

YQL query example

The example URL below showes how to call the API. It only looks complex because of the URL encoding of the YQL query. It has a simple structure really.

http://query.yahooapis.com/v1/public/yql?q=use%20%22http%3A%2F%2Fidentengine.com%2Fopentables%2Fidentities.xml%22%3Bselect%20*%20from%20identities%20where%20urls%3D%22http%3A%2F%2Ftwitter.com%2Fglennjones%22%20and%20useInwardEdges%3D1%20and%20endPoints%3D1%20and%20iconPath%3D%22http%3A%2F%2Fidentengine%2Fidenti%2Ficons%2F%22%3B&format=xml&diagnostics=false

Output stucture example

Below is an example of an object/property structure in XML. You can use the query parameter "endPoints" to switch on or off the inclusion of end point data.

<identity>
	<name>Identica</name>
	<domain>identi.ca</domain>
	<username>glennjones</username>
	<iconUrl>http://identengine/identi/icons/identica.png</iconUrl>
	<spriteClass>icon-identica</spriteClass>
	<profileUrl>http://identi.ca/glennjones</profileUrl>
	<endPoints>
		<endPoint>
			<contentType>Profile</contentType>
			<schema>hCard</schema>
			<mediaType>Html</mediaType>
			<url>http://identi.ca/glennjones</url>
		</endPoint> 
		<endPoint>
			<contentType>Status</contentType>
			<schema>hAtom</schema>
			<mediaType>Html</mediaType>
			<url>http://identi.ca/glennjones</url>
		</endPoint>
	</endPoints> 
<identity>