| description | 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.
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.
paths:
/pet:
put:
operationId: updatePet
x-stability: experimental
To mark an operation as deprecated, add the deprecated: true attribute.
paths:
/pet:
put:
operationId: updatePet
deprecated: true
Optionally specify when support ends by including x-deprecated-sunset
paths:
/pet:
put:
operationId: updatePet
deprecated: true
x-deprecated-sunset: 2030-12-05
To hide an operation from your API reference, add x-internal: true or x-gitbook-ignore: true attribute.
paths:
/pet:
put:
operationId: updatePet
x-internal: true
Add the x-hideSample: true attribute to a response object to exclude it from the response samples section.
paths:
/pet:
put:
operationId: updatePet
responses:
200:
x-hideSample: true
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:
components:
securitySchemes:
apiKey:
type: apiKey
in: header
name: Authorization
x-gitbook-prefix: Token
x-gitbook-token-placeholder: YOUR_CUSTOM_TOKEN
These extensions:
x-gitbook-prefixdefines the prefix added before the token.- example:
Authorization: <x-gitbook-prefix> YOUR_API_TOKEN
- example:
x-gitbook-token-placeholdersets the default token value.- example:
Authorization: Bearer <x-gitbook-token-placeholder>
- example:
{% hint style="warning" %}
x-gitbook-prefix is not supported for http security schemes because these schemes must follow standard IANA authentication definitions. Learn more
{% endhint %}