Pivity

The API

Last read Never
#1

The API currently does not require API keys for a number of methods. Namely script read and user read methods. This is an inconsistency and makes it harder for us to spot eventual spammers and misuse of the API. Sometimes we need to know who is accessing the API, and the easiest way for us to do this is through their API key.

To fix this issue we have decided to require an API key for all API methods. We are giving you an entire week to update your code to reflect this. Have your code fixed by Wednesday, 18th of April.

The following API routes will be affected:

GET|POST /api/scripts/

GET|POST /api/scripts/info/:id

GET|POST /api/scripts/reviews/:id

GET|POST /api/scripts/versions/:id

GET|POST /api/users/search/steam64orname

GET|POST /api/users/search/steam64/7656119xxxxx

GET|POST /api/users/banned/steam64

The fix is simply to append the api_key parameter to the request with a valid API key just like you do for any other currently protected API method.


Update: This has now been done

Agree x 23Winner x 15Disagree x 8Funny x 7Optimistic x 7Friendly x 5Dumb x 2
Users viewing this thread
Nobody