Currently, providing an invalid path when trying to use API routes results in being rerouted to the front-end. Instead, there should be a catch-all hander for the /api route that returns a JSON error response in the same format as other API error messages, and a 404 status code.
Currently, providing an invalid path when trying to use API routes results in being rerouted to the front-end. Instead, there should be a catch-all hander for the /api route that returns a JSON error response in the same format as other API error messages, and a 404 status code.