You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our app insights, I’ve noticed that API users frequently use the plural form of our endpoints, such as /quotes instead of the correct singular form, /quote. This results in a 404 error with a response like:
{
"success": false,
"message": "Not found."
}
To enhance the developer experience, we could include a helpful hint in the error response. For instance, if a plural endpoint is requested, we could respond with a message suggesting the correct singular form. This would make it easier for users to identify and correct the issue without extensive troubleshooting.
{
"success": false,
"message": "Not found. Did you mean to use the singular version of the endpoint, `/quote`?"
}
The text was updated successfully, but these errors were encountered:
In our app insights, I’ve noticed that API users frequently use the plural form of our endpoints, such as /quotes instead of the correct singular form, /quote. This results in a 404 error with a response like:
To enhance the developer experience, we could include a helpful hint in the error response. For instance, if a plural endpoint is requested, we could respond with a message suggesting the correct singular form. This would make it easier for users to identify and correct the issue without extensive troubleshooting.
The text was updated successfully, but these errors were encountered: