Download the PHP package creativecrafts/laravel-api-response without Composer

Laravel API Response

Laravel API Response is a powerful and flexible package that provides a standardized way to structure API responses in Laravel applications. It offers a range of features to enhance your API development experience, including consistent response formatting, conditional responses, pagination support, rate limiting, and more.

Table of Contents

1. [Installation](#installation)
2. [Configuration](#configuration)
3. [Basic Usage](#basic-usage)
4. [Feature](#feature)
    - [Success Response](#success-response)
    - [Error Response](#error-response)
    - [Conditional Response](#conditional-response)
    - [Pagination](#pagination)
    - [Rate Limiting](#rate-limiting)
    - [Response Compression](#response-compression)
    - [Localization](#localization)
    - [HATEOAS Links](#hateoas-links)
    - [Logging](#logging)
5. [Advanced Usage](#advanced-usage)
6. [Testing](#testing)
7. [Changelog](#changelog)
8. [Contributing](#contributing)
9. [Security Vulnerabilities](#security-vulnerabilities)
10. [Credits](#credits)
11. [License](#license)

1. Installation

You can install the package via composer:

2. Configuration

The package comes with a default configuration file that you can publish to your application using the following command:

This will create a laravel-api-response.php file in your config directory. You can customize various aspects of the package behavior in this file.

3. Basic Usage

There are two ways to use the Laravel API Response in your controllers:

Using Dependency Injection

You can inject the LaravelApi class:

Using the Facade

For a more Laravel-like experience, you can use the LaravelApiResponse facade:

4. Feature

The Laravel API Response package provides a range of features to help you build robust and reliable APIs. Here are some of the key features:

Success Responses

To return a success response:

Error Responses

To return an error response:

Conditional Responses

For responses that support caching and conditional requests:

This method automatically handles ETag and Last-Modified headers for efficient caching.

Pagination

The package supports Laravel's pagination:

Rate Limiting

Rate limiting is automatically applied to API routes. You can configure the rate limit in the laravel-api-response.php config file:

Response Compression

Response compression can be enabled or disabled in the config:

Localization

The package supports message localization. Use the localize method to translate messages:

HATEOAS Links

You can include HATEOAS links in your responses:

Logging

API responses are logged to a dedicated channel. You can configure the channel in the config file:

Exception Handling

The package includes a custom exception handler that automatically formats exceptions into consistent API responses. This is enabled by default and can be configured in the config file:

When enabled, the exception handler will automatically catch exceptions and format them into API responses with appropriate status codes. For example:

• Validation exceptions will be formatted as validation error responses
• Model not found exceptions will be formatted as 404 error responses
• Authentication exceptions will be formatted as 401 error responses
• Authorization exceptions will be formatted as 403 error responses

This ensures consistent error responses across your API without requiring extra code in your controllers.

5. Advanced Usage

The Laravel API Response package provides a range of advanced features to help you build robust and reliable APIs. Here are some of the key features:

Custom Response Structure

You can customize the response structure in the config file:

Filtering Response Fields

You can filter the fields returned in the response:

Custom Status Codes

You can specify custom HTTP status codes for your responses:

Extending with Custom Methods

The LaravelApi class uses Laravel's Macroable trait, allowing you to add custom response methods at runtime:

This makes it easy to extend the package with your own custom response types without modifying the core code.

Version 2: Breaking Changes

Version 2 of the package introduces one breaking change.

• createdResponse method has been removed. Use successResponse instead.

Testing

Changelog

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

Contributing

Please see CONTRIBUTING for details.

Security Vulnerabilities

Please review our security policy on how to report security vulnerabilities.

Credits

• Godspower Oduose
• All Contributors

License

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