Download the PHP package coliving/api-guard without Composer
On this page you can find all versions of the php package coliving/api-guard. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download coliving/api-guard
More information about coliving/api-guard
Files in coliving/api-guard
Package api-guard
Short Description A simple way of authenticating your APIs with API keys using Laravel
License
Homepage https://github.com/dungnh/api-guard
Informations about the package api-guard
ApiGuard
A simple way of authenticating your APIs with API keys using Laravel. This package uses the following libraries:
- philsturgeon's Fractal
- maximebeaudoin's api-response
Laravel 11 and PHP 8.3 is finally supported!
Laravel 5.3, 5.4 and 5.5 is finally supported!
*Laravel 5.3.x onwards: `~4.`
*Laravel 5.1.x to 5.2.x: [`~3.`](https://github.com/chrisbjr/api-guard/blob/3.1/README.md)
*Laravel 5.1.x: `~2.`
Quick start
Installation for Laravel
Run composer require coliving/api-guard
In your config/app.php
add Chrisbjr\ApiGuard\Providers\ApiGuardServiceProvider
to the end of the providers
array
Now publish the migration and configuration files for api-guard:
$ php artisan vendor:publish --provider="Chrisbjr\ApiGuard\Providers\ApiGuardServiceProvider"
Then run the migration:
$ php artisan migrate
It will setup api_keys
table.
Generating your first API key
Once you're done with the required setup, you can now generate your first API key.
Run the following command to generate an API key:
php artisan api-key:generate
Generally, the ApiKey
object is a polymorphic object meaning this can belong to more than one other model.
To generate an API key that is linked to another object (a "user", for example), you can do the following:
+php artisan api-key:generate --id=1 --type="App\User"
To specify that a model can have API keys, you can attach the Apikeyable
trait to the model:
This will attach the following methods to the model:
To generate an API key from within your application, you can use the following method in the ApiKey
model:
Usage
You can start using ApiGuard by simply attaching the auth.apikey
middleware to your API route:
This effectively secures your API with an API key which needs to specified in the X-Authorization
header. This can be configured in config/apiguard.php
.
Here is a sample cURL command to demonstrate:
You might also want to attach this middleware to your api
middleware group in your app/Http/Kernel.php
to take advantage of other Laravel features such as
throttling.
If you noticed in the basic example, you can also access the attached model to the API key by calling $request->user()
. We are attaching the related model in
this method because in most use cases, this is actually the user.
Unauthorized Requests
Unauthorized requests will get a 401
status response with the following JSON:
ApiGuardController
The ApiGuardController
takes advantage of Fractal and api-response libraries.
This enables us to easily create APIs with models and use transformers to give a standardized JSON response.
Here is an example:
Let's say you have the following model:
You can make a basic controller which will return all books like this:
Now, you'll need to make the transformer for your Book object. Transformers help with defining and manipulating the variables you want to return to your JSON response.
Once you have this accessible in your routes, you will get the following response from the controller:
More examples can be found on the Github page: https://github.com/ellipsesynergie/api-response.
To learn more about transformers, visit the PHP League's documentation on Fractal: Fractal
API Validation Responses
ApiGuard comes with a request class that can handle validation of requests for you and throw a standard response.
You can create a Request
class as you usually do but in order to get a standard JSON response you'll have to extend the ApiGuardFormRequest
class.
Now you can use this in your controller as you normally do with Laravel:
If the request failed to pass the validation rules, it will return with a response like the following:
All versions of api-guard with dependencies
illuminate/support Version ^5.4 | ^6.0 | ^7.0 | ^8.0 | ^9.0 | ^10.0 | ^11.0
illuminate/database Version ^5.4 | ^6.0| ^7.0 | ^8.0 | ^9.0 | ^10.0 | ^11.0
ellipsesynergie/api-response Version *