In past month users repeatedly reported 4xx error being printed in the SDKs. While some of these are backend issues, we still need to provide better user experience when the API key is missing or when API key scope is missing.
Recently I've added missing scope as a parameter when responding with 403, so we can tell the user exactly which scopes they need to add to proceed.
[ ] Enhance the UI of the error.
[ ] Because the meaning of 4xx errors is that user did something wrong, i don't think the number error is valuable information for them.
[ ] The red text feels scary to me
[ ] Tell users exactly how to resolve the error
[ ] When the API key is missing, we should tell them that API key is missing and they should add it in the code or via the chrome plugin with link to docs (not sure if we recognize which method they use)
[ ] When there is missing scope, we should tell them to add it and how
ZuzanaOdstrcilova
commented
1 week ago
In past month users repeatedly reported 4xx error being printed in the SDKs. While some of these are backend issues, we still need to provide better user experience when the API key is missing or when API key scope is missing.
Recently I've added missing scope as a parameter when responding with 403, so we can tell the user exactly which scopes they need to add to proceed.