seatgeek / api-support

A support channel for the SeatGeek Platform
9 stars 7 forks source link

Hello out there? Need help with a query argument #59

Open ghost opened 6 years ago

ghost commented 6 years ago

First, is anyone still actively supporting this API? It looks a little dead around here.

Second, I'm trying to construct a URL that will return an XML-formatted array of all comedy events on SeatGeek. Per the documentation, I tried submitting

https://api.seatgeek.com/2/event?type=comedy&client_id=[my client ID]&format=xml

but it didn't work. I know that XML documents for comedy events on SeatGeek include <type>comedy</type> because when I submit, for example, the following URL

https://api.seatgeek.com/2/events?performers.slug=jerry-seinfeld&client_id=[my client ID]&format=xml

it returns a document that includes all of Seinfeld's events, each of which contains <type>comedy</type>. But I want all comedy events for all comedians. I've tried constructing various URLs that include parameters for taxonomie, genre, etc. Nothing works. Any ideas?

josegonzalez commented 6 years ago

I've checked the initial query you sent me, but do not see any results which are not of type comedy. Do you have an example event ID where that is not the case?

ghost commented 6 years ago

The problem is not that the query generates results that are not of the type comedy. The problem is that the query generates only about 10 results that are of the type comedy and does not include thousands of other results that are also of the type comedy. I know these other events are on SeatGeek because I can retrieve them when I submit a query for an individual performer.

Sent from a phone

On Mar 15, 2018, at 12:29 PM, Jose Diaz-Gonzalez notifications@github.com wrote:

I've checked the initial query you sent me, but do not see any results which are not of type comedy. Do you have an example event ID where that is not the case?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

josegonzalez commented 6 years ago

We default to 10 events per page, with a maximum of 1000 (I believe, might be 10k). This is configurable via the per_page querystring parameter. You will need to paginate results using the page querystring parameter in order to get more than one page.

Hope that helps.

ghost commented 6 years ago

I added the per_page parameter and set it to 1000. Now I’m getting 50 results instead of 10 when I query events/?type=comedy. Is there another upper limit I’m running up against? There should be hundreds of results.

Sent from a phone

On Mar 15, 2018, at 1:05 PM, Jose Diaz-Gonzalez notifications@github.com wrote:

We default to 10 events per page, with a maximum of 1000 (I believe, might be 10k). This is configurable via the per_page querystring parameter. You will need to paginate results using the page querystring parameter in order to get more than one page.

Hope that helps.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

josegonzalez commented 6 years ago

So I just made the following curl request:

# fresh client id retrieved from a non-developer account
curl "https://api.seatgeek.com/2/events?type=comedy&client_id=MY_CLIENT_ID&per_page=1000&format=xml"

And had the following metadata in the response:

<meta>
    <took>52</took>
    <per_page>1000</per_page>
    <page>1</page>
    <total>11569</total>
    <geolocation>None</geolocation>
</meta>

Iterating over the results gives me 1000 results, as expected.

Are you absolutely certain that you're calling the api correctly? Perhaps your code has some other artificial limit that is stopping you from processing more than 50 events at a time?