Download the PHP package lincanbin/apidoc-markdown without Composer

apidoc-markdown

Generate API documentation in markdown format from API annotations in your source code.

Preface

All examples in this document use the Javadoc-Style (can be used in C#, Go, Dart, Java, JavaScript, PHP, TypeScript and all other Javadoc capable languages):

Install

Run

or

Creates an apiDoc of all files within dir myapp/, and put all output to dir apidoc/.

Without any parameter, apiDoc generate a documentation from all .cs .dart .erl .go .java .js .php .py .rb .ts files in current dir (incl. subdirs) and writes the output to ./apidoc/.

Command Line Interface

Show command line parameters:

Important parameters:

Configuration (apidoc.json)

The optional apidoc.json in your projects root dir includes common information about your project like title, short description, version and configuration options like header / footersettings or template specific options.

apidoc.json

If you use a package.json (e.g. in a node.js project), all apidoc.json settings can be done in package.json too, just add them under the "apidoc": { } parameter.

package.json

Settings for apidoc.json

Template specific settings

The following settings are specific for the default template of apiDoc.

Header / Footer

In your projects apidoc.json you can add a header and footer.

The title will be visible in the navigation. The filename should be a markdown textfile.

apidoc.json

Basic

In this basic example we have a small project file and an apidoc.json.

View example output

apidoc.json

From apidoc.json apiDoc get the name, version and description of your project. The file is optional (it depend on your template if the data is required).

example.js

A documentation block starts with /** and end with */.

This example describes a GET Method to request the User Information by the user's id.

@api {get} /user/:id Request User information is mandatory, without @apiapiDoc ignores a documentation block.

@apiName must be a unique name and should always be used. Format: method + path (e.g. Get + User)

@apiGroup should always be used, and is used to group related APIs together.

All other fields are optional, look at their description under apiDoc-Params.

Inherit

Using inherit, you can define reusable snippets of your documentation.

View example output

apidoc.json

example.js

In this example, a block named UserNotFoundError is defined with @apiDefine. That block could be used many times with @apiUse UserNotFoundError.

In the generated output, both methods GET and PUT will have the complete UserNotFoundError documentation.

To define an inherit block, use apiDefine. to reference a block, use apiUse. apiGroup and apiPermission are use commands to, but in their context the not inherit parameters, only title and description (in combination with apiVersion).

Inheritation only works with 1 parent, more levels would make the inline code unreadable and changes really complex.

Versioning

A useful feature provided by apiDoc is the ability to maintain the documentation for all previous versions and the latest version of the API. This makes it possible to compare a methods version with its predecessor. Frontend Developer can thus simply see what have changed and update their code accordingly.

View example output

In the example, click top right on select box (the main version) and select Compare all with predecessor.

• The main navigation mark all changed methods with a green bar.
• Each method show the actual difference compare to its predecessor.
• Green marks contents that were added (in this case title text changed and field registered was added).
• Red marks contents that were removed.

You can change the main version (top right) to a previous version and compare older methods with their predecessor.

apidoc.json

In order to avoid code bloat when API documentation changes over time, it is recommended to use a separate history file named _apidoc.js. Before you change your documentation block, copy the old documentation to to this file, apiDoc will include the historical information automatically.

_apidoc.js

example.js (your current project file)

Important is to set the version with @apiVersion on every documentation block.

The version can be used on every block, also on inherit blocks. You don't have to change the version on an inherit block, the parser check automatically for the nearest predecessor.

Full example

This is a complex example with inherit, versioning file and history file _apidoc.js, explanation is within code and generated documentation.

View example output

Files:

• _apidoc.js
• example.js
• apidoc.json

apiDoc-Params

Structure parameter like:

• @apiDefine

is used to define a reusable documentation block. This block can be included in normal api documentation blocks. Using @apiDefine allows you to better organize complex documentation and avoid duplicating recurrent blocks.

A defined block can have all params (like @apiParam), except other defined blocks.

@api

Required!

Without that indicator, apiDoc parser ignore the documentation block.

The only exception are documentation blocks defined by @apiDefine, they not required @api.

Usage: @api {get} /user/:id Users unique ID.

Example:

@apiDefine

Defines a documentation block to be embedded within @api blocks or in an api function like @apiPermission.

@apiDefine can only be used once per block

By using @apiUse a defined block will be imported, or with the name the title and description will be used.

Usage: @apiDefine MyError

Example:

For more details, see inherit example.

@apiDeprecated

Mark an API Method as deprecated

Usage: @apiDeprecated use now (#Group:Name).

Example:

@apiDescription

Detailed description of the API Method.

Usage: @apiDescription This is the Description.

Example:

@apiError

Error return Parameter.

Usage: @apiError UserNotFound

Example:

@apiErrorExample

Example of an error return message, output as a pre-formatted code.

Usage: @apiErrorExample {json} Error-Response: This is an example.

Example:

@apiExample

Example for usage of an API method. Output as a pre-formatted code.

Use it for a complete example at the beginning of the description of an endpoint.

Usage: @apiExample {js} Example usage: This is an example.

Example:

@apiGroup

Should always be used.

Defines to which group the method documentation block belongs. Groups will be used for the Main-Navigation in the generated output. Structure definition not need @apiGroup.

Usage: @apiGroup User

Example:

@apiHeader

Describe a parameter passed to you API-Header e.g. for Authorization.

Similar operation as @apiParam, only the output is above the parameters.

Usage: @apiHeader (MyHeaderGroup) {String} authorization Authorization value.

Examples:

@apiHeaderExample

Parameter request example.

Usage: @apiHeaderExample {json} Request-Example: { "content": "This is an example content" }

Example:

@apiIgnore

Place it on top of a block.

A block with @apiIgnore will not be parsed. It is usefull, if you leave outdated or not finished Methods in your source code and you don't want to publish it into the documentation.

Usage: @apiIgnore Not finished Method

Example:

@apiName

Should always be used.

Defines the name of the method documentation block. Names will be used for the Sub-Navigation in the generated output. Structure definition not need @apiName.

Usage: @apiName GetUser

Example:

@apiParam

Describe a parameter passed to you API-Method.

Usage: @apiParam (MyGroup) {Number} id Users unique ID.

Examples:

@apiParamExample

Parameter request example.

Usage: @apiParamExample {json} Request-Example: { "content": "This is an example content" }

Example:

@apiPermission

Outputs the permission name. If the name is defined with @apiDefine the generated documentation include the additional title and description.

Usage: @apiPermission admin

Example:

@apiPrivate

Defines an API as being private to allow the creation of two API specification documents: one that excludes the private APIs and one that includes them.

Usage: @apiPrivate

Command line usage to exclude/include private APIs: --private false|true

Example:

@apiSampleRequest

Use this parameter in conjunction with the apidoc.json configuration parameter sampleUrl.

If sampleUrl is set, all methods will have the api test form (the endpoint from @api will be appended). Without sampleUrl only methods with @apiSampleRequest will have a form.

if @apiSampleRequest url is set in a method block, this url will be used for the request (it overrides sampleUrl when it starts with http).

If sampleUrl is set and you don't want a method with a test form, then add @apiSampleRequest off to the documentation block.

Usage: @apiSampleRequest http://test.github.com

Examples:

This will send the api request to http://api.github.com/user/:id

This will send the api request to http://test.github.com/some_path/user/:id It overwrites sampleUrl.

This will send the api request to http://api.github.com/test/user/:id It extends sampleUrl.

This will disable the api request for this api-method.

This will send the api request to http://api.github.com/some_path/user/:id It activates the request for this method only, because sampleUrl is not set.

@apiSuccess

Success return Parameter.

Usage: @apiSuccess {String} firstname Firstname of the User.

Example:

Example with (group), more group-examples at @apiSuccessTitle:

Example with Object:

Example with Array:

@apiSuccessExample

Example of a success return message, output as a pre-formatted code.

Usage: @apiSuccessExample {json} Success-Response: { "content": "This is an example content" }

Example:

@apiUse

Include a with @apiDefine defined block. If used with @apiVersion the same or nearest predecessor will be included.

Usage: @apiUse MySuccess

Example:

@apiVersion

Set the version of an documentation block. Version can also be used in @apiDefine.

Blocks with same group and name, but different versions can be compared in the generated output, so you or a frontend developer can retrace what changes in the API since the last version.

Usage: @apiVersion 1.6.2

Example:

For more watch versioning example.