NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist · #3131 most downloaded on Packagist
JSON:API exception parsing for Laravel applications.
Last release 6 months ago
28 Mar 2026
Ships fairly regularly
a new release about every 5 months
Nearly every release is documented
notes for 10 of 10 stable releases
Nothing withdrawn
no release was ever pulled
6 years old
16 releases · first in 2021
One column per quarter.
Package now supports Laravel 13.
laravel-json-api/core v4.Package now supports Laravel 11 and 12.
Remove deprecation notices for PHP 8.4.
laravel-json-api/core v4 and v5.Package is now licensed under the MIT License.
8.2.Add debug output of previous exceptions.
Add debug output of previous exceptions.
Use HTTP status from validation exception.
Use HTTP status from validation exception.
422.Upgraded to Laravel 10 and set minimum PHP version to 8.1.
Fix accepts middleware when no matching route.
Fix accepts middleware when no matching route.
acceptsMiddleware functionality
when there is no matched route on the request.Package now supports Laravel 9.
laravel-json-api/core and laravel-json-api/validation dependencies.Initial stable release, with no changes from 1.0.0-beta.4.
Initial stable release, with no changes from 1.0.0-beta.4.
When converting an exception to the default JSON:API error, detailed exception information will now be added to the JSON:API error if the application
code member, and
the actual exception message to the detail member. The meta member will contain the exception class, file, line
number and stack trace.UnexpectedDocumentException from the laravel-json-api/spec package. The
exception has been removed from that package, and it instead throws a JsonApiException if it cannot decode a JSON
string.Multiple accept* helpers can now be added to the exception parser. This is useful when there are multiple different circumstances where you want to fo
accept* helpers can now be added to the exception parser. This is useful when there are multiple different
circumstances where you want to force the parser to render JSON:API errors - for example, if the client accepts JSON
or if the current route has the api middleware. When multiple accept helpers are used, the parser will render
JSON:API errors if any of the helpers return true.### Added - #1 The ExceptionParser now has the acceptsAll() and acceptsMiddleware() helper methods, for determining whether JSON:API errors should be
ExceptionParser now has the acceptsAll()
and acceptsMiddleware() helper methods, for determining whether JSON:API errors should be rendered.Initial beta release, no changes since alpha.2.
Initial beta release, no changes since alpha.2.
Allow the exception parser to render responses for application/json using the parser's acceptsJson() method.
application/json using the parser's acceptsJson() method.accept() method.ExceptionParser class consistent, so that they now take the exception as
the first argument and the request as the second. (Previously some had these the other way round.) This makes the
signatures consistent with the order of arguments that Laravel uses when calling render callbacks.Initial release.
Initial release.
Your coding agent can read these notes before it upgrades. Set up the MCP server →