A fully RESTful server implementation for CodeIgniter using one library, one config file and one controller.
- PHP 7.2 or greater
- CodeIgniter 3.1.10+
Note: for 1.7.x support download v2.2 from Downloads tab
Please note that version 4.0.0 is in the works, and is considered a breaking change (per SemVer). As CI 3.1.0 now has native support for Composer, this library will be moving to be composer based.
Take a look at the "development" branch to see what's up.
CodeIgniter Rest Server is available on Packagist (using semantic versioning), and installation via composer is the recommended way to install Codeigniter Rest Server. Just add this line to your composer.json file:
"chriskacerguis/codeigniter-restserver": "^3.0"or run
composer require chriskacerguis/codeigniter-restserverWhen your controller extends from REST_Controller, the method names will be appended with the HTTP method used to access the request. If you're making an HTTP GET call to /books, for instance, it would call a Books#index_get() method.
This allows you to implement a RESTful interface easily:
class Books extends CI_Controller
{
use REST_Controller {
REST_Controller::__construct as private __resTraitConstruct;
}
public function index_get()
{
// Display all books
}
public function index_post()
{
// Create a new book
}
}REST_Controller also supports PUT and DELETE methods, allowing you to support a truly RESTful interface.
Accessing parameters is also easy. Simply use the name of the HTTP verb as a method:
$this->get('blah'); // GET param
$this->post('blah'); // POST param
$this->put('blah'); // PUT paramThe HTTP spec for DELETE requests precludes the use of parameters. For delete requests, you can add items to the URL
public function index_delete($id)
{
$this->response([
'returned from delete:' => $id,
]);
}If query parameters are passed via the URL, regardless of whether it's a GET request, can be obtained by the query method:
$this->query('blah'); // Query paramREST_Controller supports a bunch of different request/response formats, including XML, JSON and serialised PHP. By default, the class will check the URL and look for a format either as an extension or as a separate segment.
This means your URLs can look like this:
http://example.com/books.json
http://example.com/books?format=json
This can be flaky with URI segments, so the recommend approach is using the HTTP Accept header:
$ curl -H "Accept: application/json" http://example.comAny responses you make from the class (see responses for more on this) will be serialised in the designated format.
The class provides a response() method that allows you to return data in the user's requested response format.
Returning any object / array / string / whatever is easy:
public function index_get()
{
$this->response($this->db->get('books')->result());
}This will automatically return an HTTP 200 OK response. You can specify the status code in the second parameter:
public function index_post()
{
// ...create new book
$this->response($book, 201); // Send an HTTP 201 Created
}If you don't specify a response code, and the data you respond with == FALSE (an empty array or string, for instance), the response code will automatically be set to 404 Not Found:
$this->response([]); // HTTP 404 Not FoundYou can overwrite all default configurations by creating a rest.php file in your config folder with your configs. All given configurations will overwrite the default ones.
You can overwrite all default language files. Just add a rest_controller_lang.php to your language and overwrite the what you want.
If your application uses language files to support multiple locales, REST_Controller will automatically parse the HTTP Accept-Language header and provide the language(s) in your actions. This information can be found in the $this->response->lang object:
public function __construct()
{
parent::__construct();
$this->__resTraitConstruct();
if (is_array($this->response->lang))
{
$this->load->language('application', $this->response->lang[0]);
}
else
{
$this->load->language('application', $this->response->lang);
}
}This class also provides rudimentary support for HTTP basic authentication and/or the securer HTTP digest access authentication.
You can enable basic authentication by setting the $config['rest_auth'] to 'basic'. The $config['rest_valid_logins'] directive can then be used to set the usernames and passwords able to log in to your system. The class will automatically send all the correct headers to trigger the authentication dialogue:
$config['rest_valid_logins'] = ['username' => 'password', 'other_person' => 'secure123'];Enabling digest auth is similarly easy. Configure your desired logins in the config file like above, and set $config['rest_auth'] to 'digest'. The class will automatically send out the headers to enable digest auth.
If you're tying this library into an AJAX endpoint where clients authenticate using PHP sessions then you may not like either of the digest nor basic authentication methods. In that case, you can tell the REST Library what PHP session variable to check for. If the variable exists, then the user is authorized. It will be up to your application to set that variable. You can define the variable in $config['auth_source']. Then tell the library to use a php session variable by setting $config['rest_auth'] to session.
All three methods of authentication can be secured further by using an IP white-list. If you enable $config['rest_ip_whitelist_enabled'] in your config file, you can then set a list of allowed IPs.
Any client connecting to your API will be checked against the white-listed IP array. If they're on the list, they'll be allowed access. If not, sorry, no can do hombre. The whitelist is a comma-separated string:
$config['rest_ip_whitelist'] = '123.456.789.0, 987.654.32.1';Your localhost IPs (127.0.0.1 and 0.0.0.0) are allowed by default.
In addition to the authentication methods above, the REST_Controller class also supports the use of API keys. Enabling API keys is easy. Turn it on in your config/rest.php file:
$config['rest_enable_keys'] = TRUE;You'll need to create a new database table to store and access the keys. REST_Controller will automatically assume you have a table that looks like this:
CREATE TABLE `keys` (
`id` INT(11) NOT NULL AUTO_INCREMENT,
`key` VARCHAR(40) NOT NULL,
`level` INT(2) NOT NULL,
`ignore_limits` TINYINT(1) NOT NULL DEFAULT '0',
`date_created` INT(11) NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;The class will look for an HTTP header with the API key on each request. An invalid or missing API key will result in an HTTP 403 Forbidden.
By default, the HTTP will be X-API-KEY. This can be configured in config/rest.php.
$ curl -X POST -H "X-API-KEY: some_key_here" http://example.com/booksCodeigniter Profiler feature has been added to the library, so that you can use the power of CI profiler in your project just by setting config parameter to enable profile through out your application Turn it on in your config/config.php file:
TRUE to turn profile ON, FALSE to turn it off
$config['enable_profiling'] = FALSE;Also you need to enable hooks in your config.php that looks like this
$config['enable_hooks'] = TRUE;Also you can refer to config/config.php.sample
This project was originally written by Phil Sturgeon, however his involvement has shifted as he is no longer using it. As of 2013/11/20 further development and support will be done by Chris Kacerguis.
Pull Requests are the best way to fix bugs or add features. I know loads of you use this, so please contribute if you have improvements to be made and I'll keep releasing versions over time.