Learn how to mark an OpenAPI API operation as experimental, deprecated or hide it from your documentation
It’s common to have operations that are not fully stable yet or that need to be phased out. GitBook supports several OpenAPI extensions to help you manage these scenarios.
Marking operation as experimental, alpha, or beta
Use x-stability to communicate that an endpoint is unstable or in progress. It helps users avoid non-production-ready endpoints. Supported values: experimental, alpha, beta.
To hide an operation from your API reference, add x-internal: true or x-gitbook-ignore: true attribute.
Hiding a response sample
Add the x-hideSample: true attribute to a response object to exclude it from the response samples section.
Customizing the authorization prefix and token placeholder
You can customize the authorization prefix (for example, Bearer, Token, or a custom string) and the token placeholder shown when using security schemes in GitBook.
In your OpenAPI spec, under components.securitySchemes, define your scheme like this:
These extensions:
x-gitbook-prefix defines the prefix added before the token.