Generate your webhook reference
Similar to API References, Fern Docs can automatically generate your webhook reference documentation from your API definition.
Fern supports webhooks through:
- OpenAPI 3.1+: Use the native
webhooks
field with anoperationId
(recommended) - OpenAPI 3.0: Use the
x-fern-webhook: true
extension - Fern Definition: Define
webhooks
in your specification
For more information on how to define webhooks, see:
Configure your webhook reference
Add a page title (api
) and reference the name of the directory where your where your webhook definition is located (api-name
).
For a real-world example of webhook documentation generated from an API definition, check out Webflow’s webhooks.
Directory structure
Your webhooks should be defined in a dedicated folder within your Fern project:
OpenAPI
Fern Definition
If you’re using OpenAPI, your generators.yml
file should point to your OpenAPI specification:
You can read more about how to define webhooks in your OpenAPI specification here.
Include more than one webhook reference
To include multiple webhook definitions in your documentation, use the webhook-name
property:
When using multiple webhook definitions, organize them in separate directories within your Fern project:
Create individual documentation pages for each webhook event
To display each webhook event as an individual page with rich examples:
OpenAPI
Fern Definition
Reference individual webhook pages using the subpackage_{tag}.{webhook-event-name}
format, where:
{tag}
is the first tag (lowercase) from your webhook definition{webhook-event-name}
is theoperationId
from your webhook definition
For OpenAPI, you must have the tags
and example
properties defined in your webhook specification.