What are you using for PHP REST API?

no you don't. rest on nette is really slow. all you need is nette di and some rest router you like.

i've been using this http://zaphpa.org/ for a few projects, then i made this https://github.com/…/rest-router for myself.

You can also try bulletphp.com

i use request signing via public and private key. you can do that yourself in few lines. or if you need something else i always wanted to try out the symfony firewall.

nette presenters add a significant overhead to rest calls. there's a lot of reflection and unnecessary services instantiation going on.

and if you want the api to be really really fast use phalcon fw :) but it's very low level

i went through all this suggestions, and finally i decided to use the restler https://github.com/…cast/Restler, trying to play with it.

it looks very lightweight, it has some authentication schemes to plug in, many examples, documentation creation, swagger ui implementation and lot of tests

seems like a good solution

that's exactly why i didn't use restler. it's already an app with given structure.

this how my index.php looks like using my lib

<?php
$configurator = require __DIR__ . '/../../app/bootstrap.php';
$container = $configurator->createContainer();

$app = new Bazo\Rest\App;
$acclimator = new \Acclimate\Container\ContainerAcclimator;
$acclimated = $acclimator->acclimate($container);
$resolver = new \Bazo\Rest\Callbacks\DefaultCallbackResolver($acclimated);
$router->setCallbackResolver($resolver);
$app->attach($router);
$app->run();
?>

and router factory

<?php
public function createRESTRouter()
	{
		$router = new Router;

		$router[] = new \Bazo\Rest\Route(['/transactions/{id}', [
				'id' => Patterns::PATTERN_ALPHA,
			]], [
			Methods::POST	 => ['@transactions', 'post'],
			Methods::GET	 => [Transactions::class, 'get'],
			Methods::PATCH	 => [Transactions::class, 'patch'],
			Methods::DELETE	 => [Transactions::class, 'delete'],
		]);

		return $router;
	}
?>

Transactions is just a regular class registered as service in config.neon with methods post, get, patch, delete.

but the lib is not complete and last update was 3 months ago.

@JanEndel But in your API you often want to use your domain logic you have already implemented in PHP (Nette) based application.

Nette is not slow, but using Nette\Application\ UI \Presenter for APIs is just stupid =)

What about something like this?

class MicroRoute extends Route {

	/** @var array */
	private $callbacks;

	/**
	 * @param  string  URL mask, e.g. '<presenter>/<action>/<id \d{1,3}>'
	 * @param  int     flags
	 */
	public function __construct($mask, $flags = 0) {
		parent::__construct($mask, function ($presenter) {
			/* @var MicroPresenter $presenter */
			$request = $presenter->getRequest();
			$method = $request->getMethod();
			if (isset($this->callbacks[$method])) {
				foreach ($this->callbacks[$method] as $callback) {
					$callback($request, $presenter);
				}
			} else {
				$presenter->error('NOT_IMPLEMENTED');
			}
		}, $flags);
	}

	public function get($callback) {
		$this->callbacks['GET'][] = $callback;
		return $this;
	}

	public function post($callback) {
		$this->callbacks['POST'][] = $callback;
		return $this;
	}

	public function delete($callback) {
		$this->callbacks['DELETE'][] = $callback;
		return $this;
	}

	public function patch($callback) {
		$this->callbacks['PATCH'][] = $callback;
		return $this;
	}

}

and then usage:

$rest = new MicroRoute('rest/<domain>/<action>');
$rest->get(function (Request $request, $presenter) {
	$parameters = $request->getParameters();
	// CODE
});
$rest->post(function (Request $request, $presenter) {

});

$router[] = $rest;