SkillFoxx

wbcli: a CLI for the Wildberries Seller API

wbcli

A conservative CLI and skill for the official Wildberries Seller API: token checks, ping, seller-info and read-only raw requests

  • 0 ★ on the repository
  • Last commit
  • MIT
CLI

Broad access

Why this level

  • The raw command sends a request with any HTTP method and body to the Wildberries API using the seller token
  • It can change prices, cards and orders; there is no separate write flag yet
All reasons and checks
Russian stack

dapi/wbcliAuthor:dapi

Install

Services

Manual install

npm install -g github:dapi/wbcli

Installs the CLI straight from GitHub; the package is not yet published to the npm registry.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • The raw command sends a request with any HTTP method and body to the Wildberries API using the seller token
  • It can change prices, cards and orders; there is no separate write flag yet

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. Among the ready commands, token:decode (parses a JWT locally), ping (checks connectivity) and seller-info (seller data) are safe. The raw command sends any request with any method and body, so it can write too. 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. The author plans dedicated write commands later behind a --write flag; until then writing is possible only through raw. 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.

Good fit when

  • You want to quickly check a token and its WB API access
  • You need a raw request to an arbitrary WB endpoint for debugging
  • You want to see rate-limit headers instead of hitting 429 blind

Not a fit when

  • You need broad write coverage: the first version has none
  • You need a published npm registry package rather than a GitHub install

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. There are no dedicated write commands, but raw accepts any HTTP method and body, and there is no write-protection flag yet. 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.

FAQ

Can wbcli change data in the WB dashboard?

No, the current version only reads and makes raw GET requests; write commands are planned for later behind a separate flag.

Where does the token come from?

Only an official Wildberries Seller API token from the seller dashboard; the skill explicitly forbids scraping private cabinet pages or reusing a browser session.

Discussion

No questions or reviews yet.

All Wildberries tools
Russian stack

A skill for the official Wildberries Seller API with local OpenAPI schemas for 286 operations and a guarded api_call helper

SkillBroad access
Russian stack

Wildberries Seller API MCP server: cards, prices, promotions, ads, orders, supplies, reviews and finance across several stores

MCP serverBroad access8
Russian stack

An Agent Skill with a full map of the Wildberries API: 12 modules, 261 methods, reference files and a call script

SkillExtended access

Wildberries Seller API skill

Wildberries Seller API - Agent Skill

Russian stack

A Wildberries Seller API reference skill on local Swagger files with search in Russian and English

SkillExtended access7

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.

README badge

Original 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.

Report a problem