Mod Portal Upload API Docs (for VSCode Extension)
Posted: Sat Jun 27, 2020 5:02 pm
I've just noticed the portal update broke my mod uploader (in the vscode mod debugger extension), and thought I might as well ask for some real docs/support this time before i start reverse engineering again to update it!
Is there (or can there be) a documented API way to get logged in for uploading, rather than scraping the login page for a form to submit? Ideally I'd love to just have you generate an oauth token (or equivalent) that can be copied into vscode for me to use, rather than having to handle user credentials directly. Can I use the service-token somehow for uploading mods?
Also, I previously only supported uploading updates to existing mods because there was no way for me to test (and thus reverse engineer) uploading new mods without spamming a ton of new mods on the portal (I keep the update testing contained/hidden by using a deprecated mod, jargtestmod). I would love some kind of "dummy" empty clone of the portal that just deletes uploaded mods after a while (an hour? a day?) for doing portal API tests against, if that's at all reasonable to create.
Is there (or can there be) a documented API way to get logged in for uploading, rather than scraping the login page for a form to submit? Ideally I'd love to just have you generate an oauth token (or equivalent) that can be copied into vscode for me to use, rather than having to handle user credentials directly. Can I use the service-token somehow for uploading mods?
Also, I previously only supported uploading updates to existing mods because there was no way for me to test (and thus reverse engineer) uploading new mods without spamming a ton of new mods on the portal (I keep the update testing contained/hidden by using a deprecated mod, jargtestmod). I would love some kind of "dummy" empty clone of the portal that just deletes uploaded mods after a while (an hour? a day?) for doing portal API tests against, if that's at all reasonable to create.