Howdy there; you're probably here to figure out how to get the [http://www.directededge.com/ Directed Edge] recommendations engine plugged into your website. Usually the best place to start is with the [[API Concepts]] and to work your way forward from there, but the brave at heart can jump straight to the [[Web Services Examples]] or [[Ruby Bindings for E-Commerce Tutorial]].

+

{|

+

|-

+

|[[Image:PHP.png|link=Getting started for PHP developers]] || [[Image:Ruby.png|link=Getting started for Ruby developers]] || [[Image:Python.png|link=Getting started for Python developers]] || [[Image:Java.png|link=Getting started for Java developers]]

+

|-

+

| [[Getting started for PHP developers]] || [[Getting started for Ruby developers]] || [[Getting started for Python developers]] || [[Getting started for Java developers]]

+

|}

−

There's a pretty big pile of information here, but don't let it intimidate you. Most web developers that already know a wee bit about databases can get up and going with our system a couple of hours. (And we're working on making it even easier.)

+

== Not using one of the languages above? ==

−

== General Information ==

+

No problem. You can still work with our API by interacting with the REST API (which is what the bindings for those languages do anyway). There's some more information on that below.

−

* [[Introduction to Recommendations]] - An introduction to how recommendations work and how they're used in E-Commerce

+

Also, '''[mailto:info@directededge.com drop us a line]'''! We prioritize which languages to support based on customer / potential customer requests.

−

== Web Services API ==

+

== How do recommendations work? ==

−

* [[API Concepts]] - General info about how things are stored in the Directed Edge graph database

+

* [[Introduction to Recommendations]]

−

* [[XML Format]] - Documentation for the XML format used with the REST API

−

* [[REST API]] - Documentation of the methods used for communicating with our servers

−

== Web Services Examples ==

+

== Our web services API: ==

−

* [[Web Services Examples]] - A collection of examples of working with the API using [http://curl.haxx.se/ curl]

+

* [[API Concepts]]

+

* [[XML Format]]

+

* [[REST API]]

+

* [[Web Services Examples]]

−

== Ruby Bindings ==

+

== Getting the most out of the recommendations on your site: ==

−

−

Our Ruby bindings make it possible to ignore all of the business with XML and REST APIs just deal with a good old fashion Ruby classes. It's still probably useful to give a read to [[API Concepts]] so that you have an idea of what the classes in the Ruby API correspond to.

We've got a handful of site-specific parameters that we can tune on our side to shape the recommendations to fit your needs. Want more popular items to show up in the recommendations? ''Can do.'' Got a trendy site where people want to discover the latest and greatest that their friends don't know about yet? Again, we're there for you.

We've got a handful of site-specific parameters that we can tune on our side to shape the recommendations to fit your needs. Want more popular items to show up in the recommendations? ''Can do.'' Got a trendy site where people want to discover the latest and greatest that their friends don't know about yet? Again, we're there for you.

How do recommendations work?

Our web services API:

Getting the most out of the recommendations on your site:

We've got a handful of site-specific parameters that we can tune on our side to shape the recommendations to fit your needs. Want more popular items to show up in the recommendations? Can do. Got a trendy site where people want to discover the latest and greatest that their friends don't know about yet? Again, we're there for you.

At the moment these parameters aren't adjustable by site administrators themselves (but that's in the pipe), but it just takes us a few seconds to tweak things to your whim.

Questions?

Feel free to drop us a mail if you've got questions on the API or if there's some content that you'd really like to see here.