Skip to main content
PATCH
Update a Docs7 site

Authorizations

Authorization
string
header
required

Get your API key at context7.com/dashboard. Treat your API key like a password and store it securely. Every key can read the management API (/v2/teamspaces/*), except personal data: member and invitation emails, library requesters, visitor questions, Docs7 reader searches, conversations, feedback and feature requests, and the GitHub account behind a build. To read those or make changes there, the key must be created with Write access ticked; other keys get 403 write_access_required.

Path Parameters

teamspaceId
string<uuid>
required

Teamspace id.

siteId
string<uuid>
required

Docs7 site id.

Body

application/json

Only the fields to change.

hosting
enum<string>

Publish a site added for the agents only. One way; delete the site to stop publishing. The only field a developer can send.

Available options:
on
slug
string
Required string length: 3 - 40
analyticsUrl
string<uri> | null
customDomain
string | null
customDomainPath
string | null
customDomainRouting
enum<string> | null
Available options:
dns,
proxy
branch
string | null
Required string length: 1 - 255
docsPath
string
context7Index
boolean
improveSchedule
enum<string>
Available options:
off,
daily,
weekly
pullRequestReview
object

PR Review Agent settings.

codeWatch
object
buildFixSchedule
enum<string>

When the Build Fix Agent fixes the issues of the latest production build (hosted sites).

Available options:
off,
after_build,
daily,
weekly
snippetSchedule
enum<string>

Whether the Example Check Agent runs every code example of the docs once a month (Docs7 Pro).

Available options:
off,
monthly

Response

The updated site

data
object
required

A Docs7 site built from a GitHub repository.

deploymentId
string<uuid> | null
required

The first build when this call published the site.

context7Notice
string | null
required

Why Context7 could not index the repository, when context7Index was turned on but the library cannot refresh.