Skip to content
SpecifyDocs

Use cases

Keep API docs up to date

Keep API docs aligned with the code so requests, responses, authentication, errors, and examples stay accurate.

API docs drift from the code faster than any other docs. Change a single parameter or response field, and anyone integrating against the docs gets stuck right away. Specify checks whether endpoint parameters, response fields, and request examples have drifted from the code and prepares proposed updates.

Set up

  1. Connect the repository with your API code

    Connect the repository and branch containing your routes, handlers, and schema definitions as the source of a document project. If your schemas live in a separate repository, add another source.

  2. Select an API reference document skill

    Select a document skill that creates an API reference, and in the focus field, describe the target readers (internal team, external partners, and so on) and the scope to cover.

  3. Turn on the push trigger

    Turn on Trigger on push for the default branch to receive a proposed update every time an API change lands.

What to check when reviewing proposed updates

AreaWhat to check
RequestsPath, method, path and query parameters, request body schema, and required fields
ResponsesResponse fields for each status code, types, nullability, and pagination format
AuthenticationRequired authentication method, scopes, and where the token is sent
ErrorsError codes and messages, and whether the request can be retried
ExamplesWhether request and response examples match the new schema
CompatibilityWhether the change breaks existing integrations, such as removing or renaming a field, and whether migration guidance is needed

Use with coding agents

Connect Specify MCP so Claude Code or Codex can reference your workspace's API docs directly while changing the API. You get to work on docs and code in the same context.