I believe we want scopes then, being a text[] (we may also just use a space delimited string for it, depending on how strict we are with the typing. The latter might be nicer to use and easy…
Should this be session based? Perhaps it would be more advisable to have scopes if we want that (or how highly we rate the user session because of eg, 2fa).
I'd put this into it's own package (eg handlers/ or http/) because it might turn big and it's not really business logic.
I don't know if I like the body to be straight up an array, even if it might make sense in the context of this specific endpoint. Are we sure there's nothing we will add to that payload?
POST /platforms/{platform}/connections/{connectedID}/emotes is UpdatePlatformExpiry ? Should this be like ReportPlatformUsage ? Also I don't understand who would call that endpoint?
so that the api can change versions without adjusting oauth2 application configuration
I don't see this as much of a real concern but having auth on a different subdomain domain is fine as…
should this be
ban?: interface {
reason: string;
start_time: string;
duration: string;
}
Or something similar? Bans will most likely contain more than just a string?
Set sounds nicer than list. There's hardly anything to go off of though