subkamran

I was upgrading my SDK and noticed some tests failing due to the return type of product_type_code. In the docs it says it should be a string, but in API responses it's always null or an empty array:

"product_code_type": [],

"product_code_value": "0-7845-3889-1",

This example is from: https://www.giantbomb.com/api/release/95369

Any ideas? Can this be fixed? For now I'm just going to ignore the value since it breaks my serialization and I don't think it will be an array once fixed.

It's been awhile, @rick any word yet? My users have been requesting this for awhile.

I've been waiting for this for years, excellent! Thank you so much! I've been proxying through a CDN this whole time (and paying for it) so this is huge.

You need to also provide a unique User-Agent HTTP header (e.g. "My Cool App/1.0")

Just a note you could use my site, http://keeptrackofmygames.com which does release tracking (with SMS and email notifications) as well as backlog/collection management :) No need to reinvent the wheel!

I still need to use the old static path, because it will respond to HTTPS (even if it's an invalid cert, I use my own CDN proxy in front of it) and my site is always-over-SSL. It'd be great if the new URLs under www.giantbomb.com could support HTTPS eventually too.

I've asked about Amazon referral links and I was told that would be okay. However, offering a subscription, ads, pay-for-access stuff, that's not allowed still.

My site is hosted on Azure (keeptrackofmygames.com), so yes, this affected me. Sent a PM to resolve it; my background jobs rely on the API. However, I'm a good citizen and I only request deltas (i.e. games/releases changed since last run date)--and I rate limit my requests myself so I don't pound the API (1req/2s usually). Awhile ago I removed the coupling from my web site itself to GiantBomb, otherwise this would have really screwed me. Again, I've said this before, if it's possible please send us emails--my API key is tied to my account which has an email; get a query going to grab those emails of API devs and send a mass email :) I found this out yesterday. Even better, if you really have to do IP blocking, let us allow IPs in a API dashboard or something. Then you can track/revoke as necessary. I thought the whole point of an API key was so you could prevent this kind of thing--I guess it depends on your hardware, at work the hardware we use can block requests before it hits web servers, so there would never be a case where you could DDoS the site if you provided an API key as long as you blocked at the hardware/load balancer level.

@edgework I sent you a PM

There's also the issue of links pointing to ".png" instead of ".jpg". Fun stuff! Icon URLs are the most reliable, if you're counting on fixed sizes.