has said, he hasn't planned how the API should work, and was open for suggestions so, here is my take on how the new API should work.
Logins/API keys
Each user can have an one or more API keys, which is obtained by logging in via a specific URL, like: "https://auth.facepunch.com/apilogin/?r=token" which then returns an API key the application will save and use.
The good thing about using API keys, is it's very easy to track who and what is misusing it, and ban them.
How posting will work
You will simply do an POST HTTP call to a thread URL like: "https://forum.facepunch.com/f/meta/otaq/Questions-about-new-API/1/", but the header will contain the API Key.
Post content format
I'm still not sure how post content should be structured when sending it trough the API. As of now, garry is using the Quill Delta format for storing post content, which in it self is fine. But it's not a very widespread format, and it currently only has a library for JavaScript.
So maybe we can use a different format for the API like markdown, where the forum parses it to the quill delta format.
Everything else
If you want to simply get a thread, a profile or a forum, you will be using GET HTTP calls.
If you think this could be done better, feel free to post your suggestions!
That sounds pretty solid 👌
i know this is old but just fyi we don't have the ability to change thread titles just yet
Ahh fair enough.
Sorry, you need to Log In to post a reply to this thread.
