lark-wiki +space-create

Create a wiki space. OpenAPI: POST /open-apis/wiki/v2/spaces. This is the project-initialization entry point — the alternative is hand-writing wiki spaces create --params '{...}'.

The underlying spaces.create API is flagged danger: true in the schema browser, but it is not confirmation-gated (no --yes). A space created by mistake is recoverable via wiki +delete-space.

Usage

lark-cli wiki +space-create \
  --name <space_name> \
  [--description <text>] \
  [--as user]

Flags

Flag	Type	Required	Default	Description
`--name`	string	Yes	—	Wiki space name. Blank/whitespace is rejected (an unnamed space is almost always an accident)
`--description`	string	No	—	Wiki space description
`--as`	enum	No	`user`	User identity only — the create API does not accept a tenant/bot token; `--as bot` is rejected upfront

Output

{
  "space_id": "7160145948494381236",
  "name": "Engineering Wiki",
  "description": "team docs",
  "space_type": "team",
  "visibility": "private",
  "open_sharing": "closed"
}

There is no url field — the create API does not return one.

Notes

Only --as user is supported; this command declares AuthTypes: ["user"] and the framework rejects --as bot with a clear message.
--dry-run previews the POST /open-apis/wiki/v2/spaces request (and surfaces the blank-name validation error early).

Required Scope

wiki:space:write_only

1.5 KiB Raw Blame History