Fix a documentation issue by generating a change request

Starts GitBook's AI on fixing a documentation issue directly: it drafts the content change and opens it as a change request for review, rather than editing content in place. This is the primary way to act on "fix issues/gaps/broken links in my docs" requests once listSiteFindings has surfaced the relevant findings. Processing is asynchronous; poll listChangeRequestsForSiteFinding for the resulting change request, then review and merge it with submitOrMergeChangeRequest.

Available in MCP

post

Authorizations

AuthorizationstringRequired

Bearer authentication header of the form Bearer <token>.

Path parameters

organizationIdstringRequired

A unique entity identifier

Pattern: ^[a-zA-Z0-9_-]+$

siteIdstringRequired

The unique id of the site

siteFindingIdstringRequired

The unique id of the site finding

Responses

202

Site finding processing has been started

No content

post/orgs/{organizationId}/sites/{siteId}/findings/{siteFindingId}/change-requests

POST /v1/orgs/{organizationId}/sites/{siteId}/findings/{siteFindingId}/change-requests HTTP/1.1
Host: api.gitbook.com
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*

202

Site finding processing has been started

No content