wbcli: a CLI for the Wildberries Seller API

Install

Manual install

npm install -g github:dapi/wbcli

This is third-party code. Review the repository files before installing.

What it does

wbcli is a small Node.js and TypeScript CLI over the official Wildberries REST API with no third-party SDK. The first version is deliberately limited to safe commands: token:decode parses a JWT locally, ping checks connectivity, seller-info returns seller data, and raw makes an arbitrary request to a given endpoint as an escape hatch. Commands can show WB's X-Ratelimit headers and, with a flag, wait and retry once on a 429. The token is read from WB_TOKEN or .env and is never logged. Write commands are planned for later and will need a separate --write flag. The repo ships a SKILL.md with safe-usage rules for agents.

Who it is for. For developers who want a lightweight CLI to check Wildberries Seller API access without a third-party SDK.

Example request

Check my Wildberries token with wbcli ping and show the remaining rate limit

Limitations

The project is early stage; the README describes it as an intentionally limited MVP. Write operations are not implemented in the first version and are planned to require a separate flag. The package is not published to the npm registry, install is straight from GitHub. You need a seller token from the WB dashboard.

How to disable. Remove the global package with npm uninstall -g wbcli, or delete your local copy.

Security check

• The first version only reads data and makes GET requests; there are no write operations yet

README in short

The README explains the Node.js and TypeScript stack choice, the MVP command list and the plan for further read-only endpoints and --write-gated write commands, install via npm install -g github:dapi/wbcli or npx, working with rate-limit headers, and an official access model limited to a seller token with no scraping of private dashboard pages.

SKILL.md

---
name: wbcli
description: "Use when working with the official Wildberries Seller API through the wbcli command-line tool: checking token scopes, testing connectivity, reading seller info, exploring read-only WB endpoints, planning data exports for Google Sheets, or debugging WB API access. This skill is for authorized seller API access only; do not use it for scraping private cabinet endpoints, bypassing permissions, or handling tokens insecurely."
---

# wbcli

Use wbcli for authorized, token-based access to the official Wildberries Seller API.

## Safety Rules

- Use only official WB Seller API tokens created in the seller cabinet.
- Never print, commit, paste, or send the token to online JWT decoders.
- Prefer read-only tokens for analytics work.
- Do not scrape private cabinet endpoints or reuse browser sessions.
- Store the token in WB_TOKEN or .env; keep .env out of git.

Related