The State of Docs Report 2025 is live! Dive in and see why docs matter more than ever:
Read the report
LogoLogo
ProductPricingLog inSign up
  • Documentation
  • Developers
  • Guides
  • Changelog
  • Help Center
  • Getting Started
    • GitBook Documentation
    • Quickstart
    • Importing content
    • GitHub & GitLab Sync
      • Enabling GitHub Sync
      • Enabling GitLab Sync
      • Content configuration
      • GitHub pull request preview
      • Commit messages & Autolink
      • Monorepos
      • Troubleshooting
  • Creating Content
    • Formatting your content
      • Inline content
      • Markdown
    • Content structure
      • Spaces
      • Pages
      • Collections
    • Blocks
      • Paragraphs
      • Headings
      • Unordered lists
      • Ordered lists
      • Task lists
      • Hints
      • Quotes
      • Code blocks
      • Files
      • Images
      • Embedded URLs
      • Tables
      • Cards
      • Tabs
      • Expandable
      • Stepper
      • Drawings
      • Math & TeX
      • Page links
    • Reusable content
    • Broken links
    • Searching content
      • Search & Quick find
      • GitBook AI
    • Writing with GitBook AI
    • Version control
  • API References
    • OpenAPI
      • Add an OpenAPI specification
      • Insert API reference in your docs
    • Guides
      • Structuring your API reference
      • Adding custom code samples
      • Managing API operations
      • Describing enums
      • Integrating with CI/CD
  • Extensions reference
  • Publishing Documentation
    • Publish a docs site
      • Public publishing
      • Private publishing with share links
    • Site structure
      • Content variants
      • Site sections
    • Site customization
      • Icons, colors, and themes
      • Layout and structure
      • Extra configuration
    • Set a custom domain
    • Setting a custom subdirectory
      • Configuring a subdirectory with Cloudflare
      • Configuring a subdirectory with Vercel
    • Site settings
    • Site insights
    • Site redirects
    • Visitor authentication
      • Enabling visitor authentication
      • Setting up Auth0
      • Setting up Azure AD
      • Setting up AWS Cognito
      • Setting up Okta
      • Setting up OIDC
      • Setting up a custom backend
  • LLM-ready docs
  • Collaboration
    • Live edits
    • Change requests
    • PDF export
    • Inviting your team
    • Comments
    • Notifications
  • Integrations
    • Install and manage integrations
    • GitHub Copilot
  • Account management
    • Plans
      • Legacy pricing
      • Sponsored site plan
      • Non-profit plan
      • Billing policy
    • Subscription cancellations
    • Personal settings
    • Organization settings
    • Member management
      • Invite or remove members
      • Roles
      • Teams
      • Permissions and inheritance
    • SSO & SAML
      • SSO Members vs non-SSO
  • Resources
    • GitBook UI
    • Keyboard shortcuts
    • Glossary
Powered by GitBook
LogoLogo

Resources

  • Showcase
  • Enterprise
  • Status

Company

  • Careers
  • Blog
  • Community

Policies

  • Subprocessors
  • Terms of Service
On this page

Was this helpful?

Edit on GitHub

Last updated 23 days ago

Was this helpful?

GitBook allows you to automatically generate pages related to the endpoints you have in your OpenAPI spec. These pages will contain OpenAPI operation blocks, allowing you and your visitors to test your endpoints and explore them further based on the information found in the spec.

Endpoints added from your spec will continue to be updated anytime your spec is updated. See the section for more info.

Automatically create OpenAPI pages from your spec

After you’ve , you can generate endpoint pages by inserting an OpenAPI Reference in the table of contents of a Space.

1

Generate pages from OpenAPI

From here, click OpenAPI Reference.

2

Choose your OpenAPI spec

Choose your previously uploaded OpenAPI spec, and click Insert to automatically add your endpoints to your space. You can optionally choose to add a models page referencing all your OpenAPI schemas.

3

Manage your API operations

GitBook will automatically generate pages based on your OpenAPI spec and the tags set inside it’s definition.

Add an individual OpenAPI block

Alternatively, you can add OpenAPI operations or schemas from your spec individually to pages throughout your docs.

1

Add a new OpenAPI block

Open the block selector by pressing /, and search for OpenAPI.

2

Choose your OpenAPI spec

Choose your previously uploaded OpenAPI spec, and click Continue to choose your the endpoints you’d like to use.

3

Choose the operations or schemas you’d like to insert

Pick the operations and the schemas you want to insert in your docs and click Insert.

In the space you’d like to generate endpoint pages, click the Add new... button from the bottom of your space’s .

Head to to learn more about organizing your operations through your OpenAPI spec.

  1. API References
  2. OpenAPI

Insert API reference in your docs

Insert complete API reference from your OpenAPI spec or pick individual operation or schemas.

  • Automatically create OpenAPI pages from your spec
  • Add an individual OpenAPI block
Structuring your API reference
added your OpenAPI spec
table of contents
Update your specification
Insert API References in the table of contents of a Space.