Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
A publisher key belongs to a publisher/developer, it is meant to be used for their own appid(s).
They can't not use their publisher api key on other developers/publishers appids.
Basically that means if they use it on their own appids they can circumvent the user privacy settings as it may be relevant for the said publisher/developer to retrieve some data from users.
https://steamcommunity.com/dev/apikey
^generate a key here and you should be good to go.
All data will retrieved in json format, so you would need to convert the json to csv on your own but that should not be an issue in itself.
Thanks a lot for your explanation. I had seen the page you linked to but I was confused because I assumed I had to link to the project I was planning to use the data for to be able to make an API key legally.
if valve by chance is reading this, they should probably reword it since the key is tied to the steam account that generates it, also perhaps just skip the "Domain Name" overall as it is pointless.