egorov-m / wb-data-service

Service for collecting information about products from Wildberries.

WbDataService

Launching (locally)

Clone the repository.

git clone https://github.com/egorov-m/wb-data-service.git

Create an .env file for the environment variables.

toucch .env

TELEGRAM_BOT_TOKEN = <token>

Build and launching containers.

docker compose up -d

Three containers are running: the Postgres database, the main REST service, and a telegram bot service running via pooling.

wb_data_service: http://localhost:8000

Launching telegram bot using Webhook.

To do this, it is necessary to additionally specify environment variables in .env. You can use Ngrok to run it locally.

TELEGRAM_BOT_MODE = webhook
TELEGRAM_BOT_WEBHOOK_URL = https://<your_domain>/webhook

In this case, three containers will also be launched. wb_data_tg_bot - service that processes data from telegram.

wb_data_service: http://localhost:8000 wb_data_tg_bot: http://localhost:8005

Usage

API

Use REST API of the main service providing the data. Swagger Docs: http://localhost:8000/docs, all supported endpoints with their descriptions can be found there.

Telegram Bot

Getting data through a Telegram bot. Commands available:

• display a list of available commands:

/help

• add a new product to the database from Wildberries by its ID:

add <nm_id>

• get the product from the database by its identifier:

get <nm_id>

• get all products created in the database:

get all

• delete a product from the database by its identifier:

delete <nm_id>

• statistics, count of products in the database with grouping by specified fields:

stat count <field_1> <field_2> ...

• statistics, count of products in the database:

stat count

• statistics, count of products in stock for the specified product:

stat quantity <nm_id>

• statistics, count of products in stock with grouping by fields:

stat quantity <field_1> <field_2> ...

• statistics, count of products in stock, among all products in the database:

stat quantity

• statistics, price history by category, like the specified product:

stat price-history <nm_id> <field_1> <field_2> ...

• statistics, price history of the specified product:

stat price-history <nm_id>

• statistics, price history by product category:

stat price-history <field_1> <field_2> ...

• statistics, price history for all products in the database:

stat price-history

• statistics, minimum maximum price of products for the last 6 months:

stat min-max-price <nm_id>

• statistics, minimum maximum price for the product for the specified count of months:

stat min-max-price <nm_id> <monthly_interval>

Examples