If an interface call returns

isv.invalid-method

(non-existent method name), it usually means the corresponding permission point is not activated. Go to Ziniao Open Platform → Application Management → Permission Management to activate it.

api

ziniao-cli api <path> [--data '{}'] [--format table] [--jq '.data[]']
ziniao-cli api GET /app/builtin/company
ziniao-cli api /superbrowser/rest/v1/erp/department/list
ziniao-cli api /superbrowser/rest/v1/erp/staff/list --data '{"page":1,"limit":10}' --format table

• Default method is POST, supports GET/POST/PUT/DELETE

• companyId

  is automatically injected by the framework and will overwrite the same field in

  --data

• --page-all

  automatically paginates (max 10 pages by default, use

  --page-limit 0

  to fetch all)

• --page-size N

  Number of items per page (default 20)

• --page-limit N

  Maximum number of pages to paginate (default 10, 0 for unlimited, used with

  --page-all

  )

• --page-delay MS

  Delay between pages in milliseconds (default 200, used with

  --page-all

  )

• --dry-run

  Preview request without execution

• --jq

  Built-in jq filtering

1. Shortcut Commands --

   staff list

   ,

   department create

   ,

   store open

   , etc. (simplified parameters, best experience)
2. General api Command --

   api <path>

   as fallback (can call any interface, requires writing JSON body)
3. zclaw invoke --

   zclaw invoke <tool>

   as fallback (can call any ZClaw tool)

_notice.update

{
  "ok": true,
  "data": ...,
  "_notice": {
    "update": {
      "current": "1.0.0",
      "latest": "1.1.0",
      "message": "ziniao-cli 1.1.0 is available, current version is 1.0.0, run npm update -g @ziniao-open/cli to update"
    }
  }
}

_notice.update

1. First complete the user's current request
2. Then display the content of the

   message

   field to the user and offer to help update
3. If the user agrees, execute

   npm update -g @ziniao-open/cli

_notice

ZINIAO_CLI_NO_UPDATE_CHECK=1

• Prohibited to output full apiKey in plain text to the terminal
• Must confirm user intent before write/delete operations

• high-risk-write

  operations (department delete, staff remove) require interactive confirmation, which can be skipped with

  --yes

• It is recommended to preview dangerous requests with

  --dry-run

  first

• ZClaw local interfaces must be called via ziniao-cli: When calling Ziniao Browser local interfaces (store/page/zclaw commands), you must use the ziniao-cli capabilities in this skill system; do not call ZClaw Bridge directly using the ziniao-assistant skill.
• Prioritize local interfaces for store lists: If the user requests to get a store list, prefer using the

  store list

  shortcut command (via local ZClaw Bridge), since regular members do not have permission for the server

  account list

  interface. The member type can be determined via the

  isBoss

  field in the result of

  ziniao-cli config show

  .
• Troubleshooting ZClaw authentication failures: If after helping the user initialize the application (

  config init

  ), requests to ZClaw interfaces still return API Key authentication failures, remind the user to go to the Ziniao Open Platform https://open.ziniao.com, check their user application's "Terminal Management" to see if the current terminal identification code (viewable in Ziniao Browser settings) has been bound.