Перейти к основному содержимому

Subtask 1-1: B2B Guide Documentation Access - Findings

Date: 2025-02-10​

Key Discovery: Documentation Location Change​

IMPORTANT: The B2B Guide documentation is NOT accessible at https://b2b-guide.lamoda.ru/ as specified in the original spec. The actual documentation is hosted at https://academy.lamoda.ru/ (Lamoda Seller Academy).

Actual Documentation Sources​

Primary Documentation URL: https://academy.lamoda.ru/​

This is the official Lamoda Seller Academy portal containing all API documentation, integration guides, and specifications.

Key Documentation Pages Found:​

  1. General API Information

  2. API Entry Points

  3. Seller Partner API vs B2B Platform API

  4. Lamoda B2B Platform API

  5. Lamoda Seller Partner API

Two API Systems Identified​

1. Seller API (JSON-RPC)​

  • Purpose: Product catalog management
  • Protocol: JSON-RPC 2.0
  • Base URL: https://public-api-seller.lamoda.ru/jsonrpc
  • Functions:
    • Nomenclature (products) management
    • Price management (FBS/FBO)
    • Stock/inventory management
    • Image uploads
    • Product attributes
    • Brand and category catalogs
  • Best for: Catalog and content management

2. B2B Platform API (REST)​

  • Purpose: Operational tasks
  • Protocol: REST
  • Base URLs:
    • Production: https://api-b2b.lamoda.ru
    • Demo: https://api-demo-b2b.lamoda.ru
  • Functions:
    • Order management (get, update, status)
    • Shipment creation and management
    • Label printing
    • Webhook notifications
    • FBO shipments
    • Delivery addresses, pickup points
  • Best for: Order processing and logistics

Authentication​

  • Method: OAuth2 with JWT tokens
  • Token TTL: 15 minutes (both APIs)
  • Credentials: client_id and client_secret (same for both APIs)
  • Support email: api-integration@lamoda.ru

Token Endpoints:​

  • Seller API: https://seller-gateway.service.lamoda.tech/jsonrpc
    • Method: v1.tokens.create
  • B2B Platform: https://api-b2b.lamoda.ru/auth/token (GET)

Environments​

Demo (Test)​

  • Purpose: Development and testing
  • Base URL: https://api-demo-b2b.lamoda.ru
  • Data: Test data only

Production​

  • Purpose: Live operations
  • Base URL: https://api-b2b.lamoda.ru
  • Data: Real orders and products

GitHub Resources​

  1. PHP SDK

  2. DTO Repository

  3. Testing Tool

Request Format​

Seller API (JSON-RPC)​

{
  "jsonrpc": "2.0",
  "method": "v1.nomenclatures.list",
  "params": {
    "seller_id": 123,
    "page": 1,
    "limit": 10
  },
  "id": "550e8400-e29b-41d4-a716-446655440000"
}

B2B Platform API (REST)​

curl -X GET 'https://api-b2b.lamoda.ru/api/v1/orders' \
  -H 'Authorization: Bearer {token}' \
  -H 'Content-Type: application/json'

Integration Scenarios​

Scenario 1: Full FBS Integration​

  1. Load catalog: Seller API (v1.nomenclatures.store, v1.nomenclature-images.update)
  2. Set prices: Seller API (v1.nomenclature.set-price)
  3. Update stock: Seller API (v1.stock.update)
  4. Get orders: B2B Platform (GET /api/v1/orders)
  5. Assembly and labels: B2B Platform (PUT /orders/{id}/collected, POST /api/v1/label/packs)
  6. Ship: B2B Platform (POST /api/v1/shipments/out)

Scenario 2: Catalog Management Only​

  • Use only Seller API

Scenario 3: FBO Integration​

  1. Load catalog: Seller API
  2. Create shipment to warehouse: B2B Platform (POST /api/v1/shipments/fulfilment)
  3. Warehouse stock: B2B Platform (GET /api/v1/stock/goods)

Key Limitations​

  • No batch processing: All operations must be done sequentially
  • Token refresh required: Every 15 minutes
  • IP whitelisting: Not supported
  • Rate limits: Not explicitly documented in available pages

Additional Resources​

Next Steps for Full Documentation​

  1. ✅ Access primary documentation sources (COMPLETE)
  2. ⏳ Access API specification pages (subtask-1-2)
  3. ⏳ Try to access Swagger UI for downloadable specs (subtask-1-3)
  4. ⏳ Document all endpoints for each API category
  5. ⏳ Document error codes and responses
  6. ⏳ Document rate limits (if available in specs)
  7. ⏳ Compile comprehensive Russian markdown documentation

Sources​