Skip FOLIO Project Navigation


For server-side projects that utilise RAML or OpenAPI (OAS), use the tool api-doc to generate API documentation from its API description files and schema and examples.

The tool is available for use during FOLIO Continuous Integration builds, and also for local use prior to commit.

This tool replaces the deprecated “generate-api-docs” (publishAPI) facility.


For use during FOLIO CI builds, refer to the Jenkinsfile configuration below.

For local use, clone the “folio-tools” repository parallel to clones of back-end project repositories, and use its api-doc facility. Refer to that document for local installation instructions.


The Python script will search the configured directories to find relevant API description files, and will process each file to generate the API documentation representation.

Where the main options are:

  • -t,--types – The type of API description files to search for. Required. Space-separated list. One or more of: RAML OAS
  • -d,--directories – The list of directories to be searched. Required. Space-separated list.
  • -e,--excludes – List of additional sub-directories and files to be excluded. Optional. Space-separated list. By default it excludes certain well-known directories (such as raml-util). Use the option --loglevel debug to report what is being excluded.

See help for the full list:

python3 ../folio-tools/api-doc/ --help

Example for RAML:

cd $GH_FOLIO/mod-notes
python3 ../folio-tools/api-doc/ \
  -t RAML \
  -d ramls

Example for both RAML and OpenAPI (OAS), i.e. when preparing for transition:

cd $GH_FOLIO/mod-foo
python3 ../folio-tools/api-doc/ \
  -t RAML OAS \
  -d ramls src/main/resources/oas


To use “api-doc” with FOLIO Continuous Integration, add this configuration to the project’s Jenkinsfile:

buildMvn {
  doApiDoc = true
  doApiLint = true
  apiTypes = 'RAML' // Required. Space-separated list: RAML OAS
  apiDirectories = 'ramls' // Required. Space-separated list
  apiExcludes = 'types.raml' // Optional. Space-separated list

Note: This tool replaces the deprecated “generate-api-docs” (publishAPI) facility. Do not use both.