I think we talked about doing something like
/recommendations/performer:1+performer:2


On Mon, Feb 4, 2013 at 5:55 PM, Adam Cohen <notifications@github.com> wrote:

> In index.html:
>
> > +          <h4>Definition</h4>
> > +          <p><code>GET http://api.seatgeek.com/2/recommendations</code></p>
> > +
> > +          <div class="example-request">
> > +            <h4>Events Similar To Taylor Swift In New York</h4>
> > +            <p><code>$ curl 'http://api.seatgeek.com/2/recommendations?performers.id=35&postal_code=10014&consumer_key=YOUR_KEY'</code></p>
> > +          </div>
> > +
> > +          <div class="example-request">
> > +            <h4>Events Similar To The New York Knicks In Los Angeles</h4>
> > +            <p><code>$ curl 'http://api.seatgeek.com/2/recommendations?performers.id=2090&postal_code=90001&consumer_key=YOUR_KEY'</code></p>
> > +          </div>
> > +
> > +          <div class="example-request">
> > +            <h4>Music Festivals Similar To Franz Ferdinand In Indio, CA In April</h4>
> > +            <p><code>$ curl 'http://api.seatgeek.com/2/recommendations/performer:9052?postal_code=92201&datetime_local.gte=2013-04-01&datetime_local.lt=2013-05-01&taxonomies.id=2010000&consumer_key=YOUR_KEY'</code></p>
>
> We support both versions in the api, but my intention was to only document
> the performers.id version, and I accidentally typed out the wrong one.I
> actually like performer:id better than performers.id= but the former has
> no logical way to support multiple performers
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/seatgeek/seatgeek.github.com/pull/5/files#r2885058>.
>
>