README

Yii2 JSON API.

Requirements

• Yii2
• ext-shared-components

Installation

Use composer and add the following line to your composer.json file:

"futuretek/yii2-api": "*"

Changelog

v1.0.0

• Initial release

Usage

Setup the API in the init method of your controller:

	public function init()
	{
		$this->setIdentity(UserModel);
		parent::init();
	}

Define the custom actions:

public function actions()
{
    return [
        ...,
        'myAction' => [
            'class' => 'futuretek\api\ApiAction',
        ],
        ...,
    ];
}

Add phpDoc tags (see below) to the properly documented actions you want:

/**
* Returns hello and the name that you gave
*
* @param string $name Your name
* @return string
* @api
*/
public function getHello($name)
{
    return ['hello' => 'Hello ' . $name];
}

Optionaly use IpFilter to limit access to API. Declare it in the behaviors() method of your controller class.

public function behaviors()
{
    return [
        'ips' => [
            'class' => \futuretek\api\IpFilter::className(),
            'policy' => IpFilter::POLICY_ALLOW_ALL,
            'list' => [
                '192.168.1.2',
                '192.168.11.1-192.168.11.27',
                '10.*.*.*',
                '172.16.1.0/24',
            ],
        ],
    ];
}

Built-in methods

ping

Ping action intended mainly to test the API interface availability

generate-definition

Generate API methods definition list

This is the default action if API method is not specified

generate-confluence-documentation

Generate API documentation in Confluence markup

Allowed phpDoc tags

@param

Usage: @param type $variable description {additional parameters}

Indicate input variable. If the input variable is an array, you can define it by using [], eg. String[]

Additional parameters

Optionally, extra attributes can be defined for each @param tag by enclosing definitions into curly brackets and separated by comma like so:

{[attribute1 = value1][, attribute2 = value2], ...}

where the attribute can be one of following:

validate - Specifies validator function to check parameter value against

Validator must be static method name from the Validate class.

• isInt
• isString

element - Array element definition. If @param is of type Array, you can describe array elements with this attribute

Usage: {element=name|type|description, element=name|type, ...}

@return

Usage: @return type description

Indicate method return value. If the return value is an array, you can define it by using [], eg. String[]

Remember: API function should always (and I mean ALWAYS!) return associative array. If another type is returned, it will be treated like the function has no output. Additionally if the function returns boolean false (or another data type that can be typed to false), the API call will result in general error message.

If you want to express processing fail inside the method, you should throw an exception.

@return-param

Usage: @return-param type name description

All API methods must return Array, bool or void(null). In case of Array you can specify each array element with this tag. This is mainly to describe the method. No additional logic is bind to this tag.

@api

Usage: @api

Indicates that this method should be accessible via API interface. Methods without this tag are ignored.

@no-auth

Usage: @no-auth

Indicates that this method will be publicly accessible without user identification

@permission

Usage: @permission permissionName

Require specified RBAC permission to run action. If @no-auth is used, this tag will be ignored

@transaction

Usage: @transaction

Run method in database transaction