When you are not able to automatically extract an API parameter definition you can use the api-parameters fence plugin to manually document them. ```api-parameters firstName, String, description with *markdown* support score, Integer, another description line with *markdown* support ``` firstName String description with markdown support score Integer another description line with markdown support

Use parent.children syntax to define nested objects like this: ```api-parameters sessionId, Integer, session Id person, Person, person to login with person.firstName, String, first name of the person person.lastName, String, last name of the person roles, List<Role>, list of authorized roles roles.id, String, role id roles.description, String, role description ``` Note: when using this approach it is necessary to explicitly define a root entry, such as person in this example. sessionId Integer session Id person Person person to login with firstName String first name of the person lastName String last name of the person roles List<Role> list of authorized roles id String role id description String role description Note: if a parameter name actually contains a period ("."), you can prevent this nesting behavior by putting the parameter name in single quotes, e.g. 'person.firstName'

Use the title parameter to specify a title. ```api-parameters {title: "Person Definition"} firstName, String, description with *markdown* support score, Integer, another description line with *markdown* support ``` firstName String description with markdown support score Integer another description line with markdown support

Use the small parameter to render API Parameters using smaller font size and occupying less width ```api-parameters {small: true} firstName, String, description with *markdown* support score, Integer, another description line with *markdown* support ``` firstName String description with markdown support score Integer another description line with markdown support

Use quotes " to wrap a multiline description. Here is an example of description including multiple lines and nested code block example. `````api-parameters cores, String, " ``` execute(cores: 10) ``` Specify how many cores to allocate for execution " gpu, Boolean, " ``` execute(cores: 10, gpu: true) ``` Specify whether to use gpu " ````` cores String execute(cores: 10) Specify how many cores to allocate for execution gpu Boolean execute(cores: 10, gpu: true) Specify whether to use gpu Note: Use larger number of backticks on outside then inside to distinct between api-parameters plugin boundaries and nested code blocks

Instead of hard-coding your parameters inside markdown files, you can specify an external JSON file. JSON could be generated based on the data you have. Some examples:build time annotation processor test time command line parameters generation Given the above file, use :include-api-parameters: api-parameters.json {title: "Person Definition"} to display it as API Parameters sessionId Integer session Id person Person person to login with firstName String first name of the person lastName String last name of the person roles List<Role> list of authorized roles id String role id description String role description Note: description field in JSON file is treated as Markdown

Each API parameter has an anchor associated with it. You need to hover over parameter name for it to appear. Use anchorPrefix parameter to avoid conflict of anchor ids when using the same API parameter names within a single page: ```api-parameters {anchorPrefix: 'customPrefix'} firstName, String, description with *markdown* support score, Integer, another description line with *markdown* support ``` firstName String description with markdown support score Integer another description line with markdown support In the example above customPrefix is added to each parameter link.