An API reference that matches your spec on every publish.

Point Workover at your OpenAPI, Swagger, AsyncAPI or GraphQL spec. Each endpoint gets a page with code samples and a Try it panel, next to the guides your team writes.

The spec changed. The reference did not.

An endpoint gains a field and the reference page still shows the old body. Readers copy a sample that fails. The guide that explains the endpoint lives somewhere else and drifts on its own schedule.

Reference pages that come from the spec.

  • Four spec formats

    OpenAPI 3, Swagger 2.0, AsyncAPI 2 and 3, and GraphQL as SDL or an introspection result.

  • Read again on publish

    Give a spec URL and every publish reads it again, so the pages match the API as it is now.

  • Samples in three languages

    Every endpoint gets cURL, JavaScript and Python samples, with its server URL and parameters filled in.

  • Versions

    Keep up to 10 versions of the site live, each with its own reference.

Try a request without leaving the page.

The Try it panel sends the request from the reader’s own browser, straight to your API. Nothing passes through Workover. If your API does not accept requests from the docs site, the panel says so and offers the request as cURL.

  • Parameter tables and response examples for every endpoint.
  • Your server URLs and OAuth scopes, read from the spec.
  • What the reader types stays in their tab, and only if they ask.

Questions

A file in your docs repository, or a URL served over HTTPS.

Start with the docs you already have.

Import them from their address, connect GitHub, and review the first suggested updates in your own workspace.