TEteaflask
authed

Put Help Site Config

Save the chrome: validate, mint the revision, advance the publish pointer — one call, one transaction. On a live site the save is public immediately; live itself is never touched. DOC_PUBLISH, not DOC_WRITE: with save=publish every config save changes the public surface, so the publish permission is the honest gate.

put/api/v1/help-site/config

Request

  • Base URL
    https://api.teaflask.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.teaflask.com/api/v1/help-site/config
  • Auth
    none declared

Request body

configobject required
parent_revision_idstring uuid nullable

Response

Successful Response

liveboolean required
public_base_urlstring nullable required

Changes

No recorded changes to this operation across all 1 revision of this API.