SponsorBlockServer
SponsorBlockServer copied to clipboard
Feature Proposal: Server responses should include a key for translations if accept header is application/json
Currently, the server responds with plain text English for errors (and without the Accept header should continue to do so for backwards compatibility).
I propose standardising error responses like so:
{
"status": 403,
"message": "User is not a VIP."
"translationKey": "__TranslationKey__"
}
Status should not be needed as that is already handled as part of the response
Seems like the API should provide the translation when using the standard "accept-language" header. The key is only useful if the extension already knows about the error.