Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Hello guys, I'm kinda newbie in Laravel Error handling. I'm playing around with API, and I needed to customize the response of ModelNotFoundException. I followed the documentation, using $this->renderable. But every time I throw an model not found exception, the result is always HttpNotFoundException. I looked into the source and I found this
* Prepare exception for rendering.
*
* @param \Throwable $e
* @return \Throwable
*/
protected function prepareException(Throwable $e)
{
if ($e instanceof ModelNotFoundException) {
$e = new NotFoundHttpException($e->getMessage(), $e);
} elseif ($e instanceof AuthorizationException) {
$e = new AccessDeniedHttpException($e->getMessage(), $e);
} elseif ($e instanceof TokenMismatchException) {
$e = new HttpException(419, $e->getMessage(), $e);
} elseif ($e instanceof SuspiciousOperationException) {
$e = new NotFoundHttpException('Bad hostname provided.', $e);
} elseif ($e instanceof RecordsNotFoundException) {
$e = new NotFoundHttpException('Not found.', $e);
}
return $e;
}
So I want to ask why the team did that ? Also another question Why in the documentation there's nearly nothing about the render() method ? Thank you ♥
Because you are making an HTTP request and the resource was not found. No need to give away too much information about what is the exact error since it doesn't matter to the end-user.
Documentation is open source so if you notice something is missing you can add it.
I needed to customize the response of ModelNotFoundException.
@koossay You don’t. If a user’s making a request for a resource and that resource (model) doesn’t exist, then a 404 Not Found is the appropriate response.
“Hey, server, get me this object.”
“Sorry, no. It doesn’t exist.”
I guess I didn't explain too much, my bad. What I meant is what if I'm building an API, the ModelNotFoundException is rendered to the appropriate view, but I need a JSON response. I can do that in the controller with return response()->json(); But I want things to work smoothly. However I managed it to work only in the API. Also Thank you @bugsysha, you made things clear, not too much information is generally a good thing.
What I meant is what if I'm building an API, the ModelNotFoundException is rendered to the appropriate view, but I need a JSON response
@koossay You’ll get a JSON response if you tell the server you want a JSON response. If you send your requests with a Accept: application/json header, then the server will send you back a JSON response.
I can do that in the controller with return response()->json(); But I want things to work smoothly.
As above. If you’re just hitting API URLs in the browser then it’s going to include a header of Accept: */*, which translates to, “Hey, server, I’ll accept anything”. So Laravel will, be default, return you a HTML view.
So if you want JSON, you need to specify in your request that’s what you’ll accept.
This is interesting, this my first time dealing with API's , I will try it. Thank your for your response.
It’s probably worth getting familiar with common parts of HTTP if you’re going to build a HTTP-based API. So familiar with things like common request and response headers, status codes and their intended usages, etc.
Please or to participate in this conversation.