Odd Behavior / Possible Bug

Avatar image for paulwgraham
paulwgraham

85

Forum Posts

0

Wiki Points

0

Followers

Reviews: 0

User Lists: 0

#1  Edited By paulwgraham

Every call to the search endpoint with resources=platform returns an empty array for "results". Similar to how the search endpoint responds when the parameter "page" is set to too large of a number.

To be fair "platform" isn't listed as an officially supported resource in the API documentation. However, it is supported when searching using the site and the malformed response (in lieu of an error) makes me think this could just be a bug.

For example:

Consider searching for platforms using the site:

https://www.giantbomb.com/search/?i=platform&q=nes

Versus attempting to search for platforms using the API:

curl -X GET -H "User-Agent: exampleapp" "https://www.giantbomb.com/api/search/?api_key=[API_KEY]&format=json&query=nes&resources=platform"

returns the following:

{

"error":"OK",

"limit":10,

"offset":0,

"number_of_page_results":10,

"number_of_total_results":36,

"status_code":1,

"results":[],

"version":"1.0"

}

Notice the empty array for "results". Requesting a different page the offset changes but "results" remains empty.

curl -X GET -H "User-Agent: exampleapp" "https://www.giantbomb.com/api/search/?api_key=[API_KEY]&format=json&query=nes&resources=platform&page=2"

returns the following:

{

"error":"OK",

"limit":10,

"offset":10,

"number_of_page_results":10,

"number_of_total_results":36,

"status_code":1,

"results":[]

,"version":"1.0"

}

Avatar image for paulwgraham
paulwgraham

85

Forum Posts

0

Wiki Points

0

Followers

Reviews: 0

User Lists: 0

Quick note: I poked at this for a minute this morning trying to find the happy path and I can report (unsurprisingly) that this doesn't work with the xml format either.