DO NOT USE THIS PACKAGE FOR NEW PROJECTS - USE laravel-json-api/laravel INSTEAD.
This package has now been rewritten, substantially improved and released as the laravel-json-api/laravel
package.
Documentation for the new version is available on our new website laraveljsonapi.io and the
code is now developed under the
Laravel JSON:API Github organisation.
The cloudcreativity/laravel-json-api
package is now considered to be the legacy package. As we know it is in use in
a lot of production applications, it will continue to receive bug fixes and updates for new Laravel versions. However,
it is no longer supported for new features.
If you are starting a new project, you MUST use the
new package laravel-json-api/laravel
.
Build feature-rich and standards-compliant APIs in Laravel.
This package provides all the capabilities you need to add JSON API compliant APIs to your application. Extensive support for the specification, including:
The following additional features are also supported:
From jsonapi.org
If you've ever argued with your team about the way your JSON responses should be formatted, JSON API is your anti-bikeshedding weapon.
By following shared conventions, you can increase productivity, take advantage of generalized tooling, and focus on what matters: your application. Clients built around JSON API are able to take advantage of its features around efficiently caching responses, sometimes eliminating network requests entirely.
For full information on the spec, plus examples, see http://jsonapi.org.
Full package documentation is available on Read the Docs.
Join the Laravel JSON:API community on Slack.
Laravel | This Package |
---|---|
^9.0 |
^4.0 |
^8.0 |
^3.0|^4.0 |
^7.0 |
^2.0 |
^6.0 |
^1.7 |
5.8.* |
^1.7 |
5.7.* |
^1.0 |
5.6.* |
^1.0 |
5.5.* |
^1.0 |
Make sure you consult the Upgrade Guide when upgrading between major or pre-release versions.
Apache License (Version 2.0). Please see License File for more information.
Installation is via composer
. See the documentation for complete instructions.
Contributions are absolutely welcome. Ideally submit a pull request, even more ideally with unit tests. Please note the following:
master
branch.develop
branch.We recommend submitting an issue before taking the time to put together a pull request.