How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

GitBook Space Content API

Manage pages and content within a space.

GitBook Space Content API is one of 19 APIs that GitBook publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

This API exposes 7 JSON Schema definitions.

Tagged areas include Space Content. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an AsyncAPI specification, a JSON-LD context, and 7 JSON Schemas.

This API exposes 4 operations across 3 paths, and defines 4 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against a single base URL, https://api.gitbook.com/v1.

4 operations 3 paths 4 schemas 3 GET1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Server
https://api.gitbook.com/v1
Authentication
HTTP Bearer
Contact
Resource Areas
1

Authentication & Security 1

GitBook Space Content API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (token) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — API access token. Generate one from the Developer settings of your GitBook user account.

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 3 GET, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Space Content 4

Manage pages and content within a space.

GET
/spaces/{spaceId}/content
GitBook Get space content
getSpaceContent 1 param → 200401404
GET
/spaces/{spaceId}/content/page/{pageId}
GitBook Get a page in a space
getPageInSpace 2 params → 200401404
PUT
/spaces/{spaceId}/content/page/{pageId}
GitBook Update a page in a space
updatePageInSpace 2 params body → 200401404
GET
/spaces/{spaceId}/content/files
GitBook List files in a space
listFilesInSpace 3 params → 200401404

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Page (7 properties), File (4 properties), Pagination (1 property), Error (1 property). Each schema is shown below with its type and property counts.

Error
object
1 property
File
object
4 properties
Page
object
7 properties
Pagination
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

gitbook-space-content-api-openapi.yml Raw ↑

Other APIs GitBook publishes across the network.

GitBook Change Request Content API
GitBook Change Request Reviewers API
GitBook Change Requests API
GitBook Collections API
GitBook Custom Hostnames API
GitBook Docs Sites API
GitBook Imports API
GitBook Integrations API
GitBook OpenAPI Specs API
GitBook Organization Members API
GitBook Organization Teams API
GitBook Organizations API
Where this information came from

This is an independent, third-party profile of GitBook Space Content API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.