Download the PHP package kennedy-osaze/laravel-api-response without Composer

Laravel API Response is a package that helps to provide and render a consistent HTTP JSON responses to API calls as well as converting and formatting exceptions to JSON responses.

Version Compatibility

Installation

You can install the package via composer:

You can publish the translation files using:

This will create a vendor folder (if it doesn't exists) in the lang folder of your project and inside, a api-response/en folder that has two files: errors.php and success.php. Both files are used for the translation of message strings in the JSON response sent out.

Optionally, you can publish the config file using:

Usage

Using Package Traits

This package provides two traits that can be imported into your projects; namely:

• The \KennedyOsaze\LaravelApiResponse\Concerns\RendersApiResponse trait which can be imported into your (base) controller class, middleware class or even your exception handler class
• The \KennedyOsaze\LaravelApiResponse\Concerns\ConvertsExceptionToApiResponse trait which should only be imported into your exception handler class.

So we can have on the base controller class (from which all other controller may extend from):

Or some random controller class:

In any case, you have access to a load of methods which you can call to render your data. This includes:

Also to handle exceptions, converting them to API response by using the \KennedyOsaze\LaravelApiResponse\Concerns\ConvertsExceptionToApiResponse trait in your exception handler which provides the renderApiResponse public method and this can be used as follows:

You could also use the renderable method of the handler class:

Using Package Classes

At the core of the above methods, there is an underlying ApiResponse class being called that can also be used as follows:

If you would like to change the format for validation errors, you may call the registerValidationErrorFormatter static method of the ApiResponse class in the boot method of your App\Providers\AppServiceProvider class or any other service provider you want. You can do something like this:

Response Data

The response data $data to be rendered for successful response can be any of the following type:

• array e.g. ['name' => 'Dummy']
• standard object e.g. new stdClass
• integer e.g. 1
• boolean e.g. true
• any Model object, instance of \Illuminate\Database\Eloquent\Model
• any Collection object, instance of \Illuminate\Support\Collection
• any JsonResource object, instance of \Illuminate\Http\Resources\Json\JsonResource
• any Jsonable object, instance of \Illuminate\Contracts\Support\Jsonable
• any JsonSerializable object, instance of \JsonSerializable
• any Arrayable object, instance of \Illuminate\Contracts\Support\Arrayable

Any of the above can be used stored as $data and used thus:

For API Resources JsonResources , you can create JSON responses by doing the following:

Response Messages

This package uses translation files to translate messages defined when creating responses. This packages, as described earlier, comes with two translation files: success.php and errors.php. The success.php contains translations for success response messages while errors.php contains that of error response messages.

Given that you have a success.php translation file as thus:

The ApiResponse class would be able to translate messages as follows:

This is similar to how messages for error responses are translated except with the fact that the error messages are read from the errors.php translation file instead (or whatever you specify in the config file).

Also, for error messages, you can decide that error response should have error codes. You can provide error codes in your responses in a couple of ways:

Also, you can use the errors.php translation file to translate error codes. Given the below errors.php file:

We can have a response with error code as follows:

Testing

Changelog

Please see CHANGELOG for more information on what has changed recently.

Contributing

Please see CONTRIBUTING for details.

Security Vulnerabilities

If you discover any security related issues, please email [email protected] instead of using the issue tracker.

Credits

• Kennedy Osaze
• All Contributors

License

The MIT License (MIT). Please see License File for more information.