30 June: Multiple breaking changes to ownership, paths & change-requests in the GitBook API
We’ve removed the /v1/owners/:id/spaces endpoint in favor of more explicit replacements
Breaking: removing /v1/owners/:id endpoints
/v1/owners/:id endpointsEndpoint /v1/owners/:id/spaces has been removed and replaced by:
/v1/orgs/:id/spacesfor an organization/v1/users/:id/spacesfor a user
Breaking: path and slug properties in pages
path and slug properties in pagesPage previously had only one path property representing the page slug in its direct page parent. Pages will now include 2 properties:
slug: representing the page's slug in its direct parentpath: representing the complete page's path in the revision
Breaking: url path parameter for page lookup by path
url path parameter for page lookup by pathRequests on page using a URL will now require a URL encoded page's path. For example the previous request:
GET /v1/spaces/u23h2u4hi24/content/url/a/b/cshould now be:
GET /v1/spaces/u23h2u4hi24/content/path/a%2Fb%2FccreateChangeRequest returns entire change-request
createChangeRequest returns entire change-requestPreviously POST /v1/spaces/:space/change-requests was only returning the ID of the newly created change-request.
The response will now contain the entire change-request object. A property changeRequest is appended for compatibility, but marked as deprecated and will be removed in the near future.
Last updated
Was this helpful?