MIME-Version: 1.0
Received: by 10.150.45.42 with SMTP id s42mr52034ybs.3.1255637404354; Thu, 15 
	Oct 2009 13:10:04 -0700 (PDT)
Date: Thu, 15 Oct 2009 13:10:04 -0700 (PDT)
In-Reply-To: <15A53316-C957-4C42-8CD6-7D2C4954AC3C@gmail.com>
X-IP: 69.181.1.244
References: <69163fb9-1a28-4a3f-b47a-9848d2b18364@12g2000pri.googlegroups.com> 
	<7d24c161-1455-45ea-8eb0-0c6dc7cbbadc@2g2000prl.googlegroups.com> 
	<ccd3776b0910141655i9214efcjeafead70a30c5488@mail.gmail.com> 
	<15A53316-C957-4C42-8CD6-7D2C4954AC3C@gmail.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_1; en-us) 
	AppleWebKit/531.9 (KHTML, like Gecko) Version/4.0.3 Safari/531.9,gzip(gfe),gzip(gfe)
Message-ID: <b0609a2b-bd7b-452f-8510-79691bfdb9ae@12g2000pri.googlegroups.com>
Subject: Re: XML for only top10
From: Ingo Muschenetz <ingo.muschen...@gmail.com>
To: What The Trend API <what-the-trend-api@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

JSON for top 10 with descriptions is now available:

http://api.whatthetrend.com/api

We'll move all functions to api.whatthetrend.com to make it an easier
devision between the site and the API.

On Oct 14, 5:03=A0pm, Ingo Muschenetz <ingo.muschen...@gmail.com> wrote:
> It's not public yet. We'll publish the details on the beta API page =A0
> tomorrow.
>
> Note that they JSON is _identical_ to the Twitter one, just with a few =
=A0
> extra properties, to make it easier to use for someone switching.
>
> -Ingo
>
> On Oct 14, 2009, at =A0Oct14 4:55 PM, Stephen Cerruti wrote:
>
>
>
> > The JSON is what I need, I missed it, can you point me at the right =A0
> > call?
>
> > On Wed, Oct 14, 2009 at 4:51 PM, Ingo Muschenetz <ingo.muschen...@gmail=
.com
> > > wrote:
>
> > We've created a JSON for that. Would you want the exact same XML
> > format as the other responses?
>
> > Best,
> > Ingo
>
> > On Oct 5, 12:38 am, Meph <badmephi...@gmail.com> wrote:
> > > It would be amazing if there was an XML only for the currently top10
> > > trending topics on Twitter. It would save you a lot of bandwidth, =A0
> > and
> > > me a lot of hassle having to do two separate requests to you &
> > > twitter.
> > > And I don't think I'm alone.
>
> > > Keep up the good work,