API Documentation #8

Closed
opened 2013-12-14 17:18:58 +00:00 by joshtronic · 0 comments
joshtronic commented 2013-12-14 17:18:58 +00:00 (Migrated from github.com)

Simple documentation outlining the API end points and auth and all of that good stuff.

I'm thinking JS won't be available by default and will have to be enabled in the settings because of the potential for fraudulent activity against the API.

Wondering how the API should be auth, does each leaderboard have a key or does the account have a key and the leaderboard can be called by name? Key per leaderboard would require less information to be transmitted. Perhaps there needs to be a key and a secret that are both required along with the leaderboard identifier?

I dunno, will figure out when I get there.

Simple documentation outlining the API end points and auth and all of that good stuff. I'm thinking JS won't be available by default and will have to be enabled in the settings because of the potential for fraudulent activity against the API. Wondering how the API should be auth, does each leaderboard have a key or does the account have a key and the leaderboard can be called by name? Key per leaderboard would require less information to be transmitted. Perhaps there needs to be a key and a secret that are both required along with the leaderboard identifier? I dunno, will figure out when I get there.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: joshtronic/leaderbin#8
No description provided.