ChrisSD: Well presumably their client will have access to this data so it'd already be available because they can't really stop people from hacking together an application that uses unofficial APIs (see the linux downloader). Also people already scrap the HTML from GOG.com, which causes more traffic then a simple API would.
Wishbone: Yes, but the thing about HTML scraping is that it's not done in real-time. The MaGOG search engine for instance scrapes the catalog once a day and caches the data, then all searches in the engine are done in the cached data. That's what, 700 page views in a day? Not a lot, anyway. However, had the search engine been made with a GOG API, it would call the GOG servers every time it was used. Less data would be transferred per call of course, but there would be a
lot more calls.
And that's just the game catalog. Imagine the server load a forum search API could make.
Why couldn't it cache results? It still could. In fact if that is a major concern, GOG could provide an api that delivers all results in one single request which could be cached for, say. 6 hours by MaGog's servers.
Look, if someone wants to be abusive towards GOG's services they can be whether or not GOG.com has an official API. An API just provides away for responsible people to interact with GOG's services while having a known limit (e.g. just about every API on the planet says something like "you may make X requests within Y time with responses being no larger than Z").