Download the PHP package baraja-core/structured-api without Composer
On this page you can find all versions of the php package baraja-core/structured-api. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download baraja-core/structured-api
More information about baraja-core/structured-api
Files in baraja-core/structured-api
Package structured-api
Short Description Complex library for definition of your structured API endpoint as class with schema.
License
Homepage https://github.com/baraja-core/structured-api
Informations about the package structured-api
Structured REST API in PHP
Full compatible smart structured API defined by schema.
- Define full type-hint input parameters,
- Validate returned data by schema,
- Full compatible with Nette framework,
- Inject dependencies by
#[Inject]
attribute (or old@inject
annotation syntax) in public property.
📦 Installation & Basic Usage
This package can be installed using PackageRegistrator which is also part of the Baraja Sandbox. If you are not using it, you have to install the package manually following this guide.
A model configuration can be found in the common.neon
file inside the root of the package.
To manually install the package call Composer and execute the following command:
🛠️ API endpoint
API endpoint is simple class with action methods and dependencies. For best comfort please use your custom BaseEndpoint with declaring all required dependencies.
Simple example:
Method actionDefault
is used for request in format /api/v1/test
with query parameter ?hello=...
.
Method postCreateUser
will be called by POST request with all data.
Always return the response from the endpoint directly as the return type of the method. This makes static analysis easier for other tools (for example, for checking code integrity or generating documentation). The sendJson()
, sendOk()
, and sendError()
methods are still supported, but may be marked as deprecated in the future.
📝 Endpoint registration
If you use the Nette Framework, all endpoints will be registered automatically. This provides an extension for DIC.
To register automatically, simply inherit BaseEndpoint
or implement the Baraja\StructuredApi\Endpoint
interface.
🌐 HTTP methods
The library supports all HTTP methods for the REST API. The selection of the HTTP method is solved by the method name.
You can specify the HTTP method at the beginning of the method name, or use an alias:
List of aliases (aliases are optional):
action
asGET
update
asPUT
create
asPOST
💾 Obtaining raw data
For processing complex data structures, it may be useful to obtain the data in its original raw form.
The library reserves the key variable array $data
, which always contains the original input values from the user, regardless of validation.
For example:
✅ Validation
In the runtime, when calling methods, the passed arguments against the method definition and data types are validated. This ensures that the endpoint is never called with incorrect data.
The library guarantees that you will always get the data in the type you request. If you need to define the type more complicated, you can use a comment annotation.
Combined example:
The library takes full advantage of PHP 7 and always checks data types. If the data is passed in the wrong type (for example, a boolean cannot be passed by the GET method), it performs an automatic conversion or throws an error.
If the argument contains a default value, it is automatically marked as optional. If the user does not pass a value, the default is used. All mandatory arguments must always be passed, if not, your logic will not be called at all.
🙋 Smart response
The library contains a number of built-in methods for elegant handling of all important return states.
For example, if we want to get the detail of an article by ID and return its detail from the database, the use is completely intuitive:
Each method can return output either via send
methods or directly as a type object. A more modern approach is to return the entire object, as this gives us type checking and the underlying basis for automatically generated documentation.
Warning: If you do not pass any output (by method or return statement), endpoint processing will fail.
When processing actions, it is a good idea to return success or error information:
🔒 Permissions
🚩Warning: If you do not set the rights at all, by default all endpoints are private and you must log in to call them! 👮
All API requests are validated at runtime. If you want to allow all users access to your endpoints, please add the #[PublicEndpoint]
attribute to class.
For example (this endpoint will be public):
To restrict rights, define an #[Role]
attribute over a class or method.
For example (only administrators and moderators can call this endpoint):
Rights settings can also be combined. For example, in a public endpoint, restrict rights to a specific method only:
🔒 Check API token
If you want to provide the API to your external partners or to provide secure communication with another application, it is a good idea to use authentication of all requests via an API token. There is an official extension structured-api-token-authorizer for this use.
🗺️ Project endpoint documentation
When developing a real application, you will often need to pass work between the backend and the frontend.
To describe all endpoints, the package offers an optional extension that generates documentation automatically based on real code scanning.
Try the Structured API Documentation.
📄 License
baraja-core/structured-api
is licensed under the MIT license. See the LICENSE file for more details.
All versions of structured-api with dependencies
ext-json Version *
ext-mbstring Version *
ext-iconv Version *
baraja-core/service-method-invoker Version ^2.2.1
baraja-core/url Version ^1.1
baraja-core/serializer Version ^1.0
nette/di Version ^3.0
nette/http Version ^3.1
nette/application Version ^3.1
nette/robot-loader Version ^3.3
nette/caching Version ^3.1