Skip to main content


The /sys/internal/specs/openapi endpoint is used to generate an OpenAPI document of the mounted backends. The response conforms to the OpenAPI V3 specification, with path names matching the mount names used by the OpenBao server (i.e. customizations with -path will be reflected). The set of included paths is based on the permissions of the request token.

The response may include OpenBao-specific extensions. Three are currently defined:

  • x-vault-sudo - Endpoint requires sudo privileges.
  • x-vault-unauthenticated - Endpoint is unauthenticated.
  • x-vault-create-supported - Endpoint allows creation of new items, in addition to updating existing items.

Basic documentation will be generated for all paths, but a newer path definition structure now allows for more detailed documentation to be added. At this time the /sys endpoints have been updated to use the new structure, and other endpoints will be modified incrementally.

Get OpenAPI document

This endpoint returns a single OpenAPI document describing all paths visible to the requester.



  • generic_mount_paths (bool: false) – Used to specify whether to use generic mount paths. If set, the mount paths will be replaced with a dynamic parameter: {mountPath}

Sample request

$ curl

Sample response

"openapi": "3.0.2",
"info": {
"title": "OpenBao API",
"description": "HTTP API that gives you full access to OpenBao. All API routes are prefixed with `/v1/`.",
"version": "1.0.0",
"license": {
"name": "Mozilla Public License 2.0",
"url": ""
"paths": {
"/auth/token/create": {
"description": "The token create path is used to create new tokens.",
"post": {
"summary": "The token create path is used to create new tokens.",
"tags": [
"responses": {
"200": {
"description": "OK"