Birinchi Shop

Changelog and API versioning policy

For partners, developers and tracker owners: dated technical changes to the platform, newest first. Entries marked "affects /api/v1" changed an API response or behavior. Below are the rules for how the API version changes.

Sign up free
1 minute · no card or documents
30,000+UZS per delivered order
14 minmedian payout time (last 90 days)
350+active products
0 UZSto start
Data as of 2026-11-21. Payout term: within 1 day; 14 min is the actual median over the last 90 days. How the numbers are counted

Changes

New features and announcements for partners — Platform news.

  1. Integration
    n8n connector and SDK 0.2.0

    An official n8n connector is out: npm package n8n-nodes-birinchishop (actions and a signature-verified webhook trigger; install via n8n → Settings → Community nodes). Node.js and Python SDK 0.2.0 (npm, PyPI): test-key mode, test order status changes, typed error classes. GitHub · API docs

  2. Integration
    Browser notifications (Web Push)

    In the partner panel, personal notifications (order accepted, delivered, earnings) now arrive even when the browser is closed: Profile → Browser notifications. You choose which kinds to receive (orders, withdrawals, bonuses, ads, offers, tips). Standard Web Push; on iPhone the panel must be added to the Home Screen. After sign-out or remote sign-out of a device, no notifications are sent to it. Technical capabilities

  3. API affects /api/v1
    Cohort analysis and multi-touch attribution report

    Two new statistics reports. Cohort analysis: by the week an order was created, the share delivered within 3, 7, 14 and 30 days (GET /stats/cohorts). Multi-touch attribution: first, last and assisting touches for an order placed through a link or landing page (GET /stats/attribution); this uses a first-party cookie with no personal data in the shopper's browser (privacy policy, clause 5.3). The payout rule is unchanged: an order is credited to the link it was placed through. Technical capabilities · API docs

  4. Docs
    Official PHP SDK (beta)

    Official library for PHP 8.1+, version 0.1.0: zero dependencies, every API method, safe retries, Idempotency-Key, webhook signature verification and test-key (bsk_test_) mode. Install: composer require birinchishop/birinchishop. Source: github.com/Birinchishop/birinchishop-php. GitHub · API docs

  5. Security
    Active devices, sign-in history, data export, HSTS preload

    New profile sections: a list of signed-in devices with remote sign-out, sign-in history and new-device alerts; a self-service export of your own data as a single JSON file (customer phones and document numbers are masked). The site was submitted to the HSTS preload list, and the origin server now accepts only connections presenting the CDN certificate. Independent ratings: Mozilla Observatory A+ (score 115), Qualys SSL Labs A+. Technical capabilities · Data protection

  6. MCP / AI
    A2A (Agent2Agent 1.0): shop and partner agents

    Other AI agents can now reach the platform over the A2A protocol. The shop agent is public: card at /.well-known/agent-card.json, endpoint /api/a2a/shop (JSON-RPC and HTTP+JSON). The partner agent: card at /api/a2a/partner/agent-card.json, authenticated with an API key or OAuth; scopes and test mode are the same as in API v1. Orders are placed only after the shopper explicitly confirms. No streaming or push notifications. Technical capabilities · API docs

  7. Security
    Passwordless sign-in with passkeys

    Sign in to the partner panel from the browser with a fingerprint, Face ID or screen lock (WebAuthn). Passkeys are added, renamed and removed in the profile; adding one requires a login within the last 10 minutes or the current password. A password reset removes all passkeys. Not in the Android app yet. Technical capabilities · Data protection

  8. API affects /api/v1
    Sale chance: ML model

    The sale chance of a new order now comes from an ML model trained on our own order history (retrained weekly). The factors list in API v1 and MCP responses has a new factor: ml (value and main drivers). For new orders the percentage is lower than before and closer to real delivery. The score is informational only. Technical capabilities · API docs

  9. Docs
    Official Node.js and Python SDKs (beta, npm and PyPI), Postman collection, Binom guide

    Official SDKs, version 0.1.0 (beta): Node.js 18+ (zero dependencies, TypeScript types, webhook signature verification) and Python 3.8+ (standard library only, type hints). Published on npm and PyPI: npm install birinchishop, pip install birinchishop; source code on GitHub. The examples repo gained a Postman collection and a Binom setup guide. npm · PyPI · Node.js SDK · Python SDK · Postman · Binom

  10. Tracking affects /api/v1
    Postback macro {payout_earned}

    New macro: the payout amount only when conversion_status=sale (delivered), 0 in every other status. Use it for revenue in your tracker. {payout} is unchanged — the offer payout in every status. Postback guide · API docs

  11. API affects /api/v1
    API test mode (sandbox)

    Test keys (bsk_test_…) can be created in the panel. Read requests return real data; POST /orders and POST /links run the same checks as with a live key, but no order or link is created and nobody is called — responses carry "test": true and an X-Birinchishop-Mode: test header. A signed test webhook (order.created) follows a test order; POST /api/v1/sandbox/orders/{id}/status simulates status changes (webhooks and postbacks, new {test} macro = 1). Test objects are kept for 24 hours (cleared if the server restarts); test keys cannot manage ads; MCP works with test keys too. guide.md · API docs · OpenAPI

  12. Infrastructure
    In-flight requests survive restarts (graceful restart)

    During updates the server shuts down gracefully: it stops accepting new connections, finishes in-flight requests (such as order creation), closes real-time (SSE) connections cleanly and the panel reconnects by itself. Previously the process could stop immediately and cut off a running request. The effect in production has not been measured yet. /status

  13. Docs
    Legal documents in ru/en at their own URLs

    The Russian and English texts of the partner agreement, public offer and privacy policy now have their own URLs (/ru/…, /en/partner-agreement, /en/public-offer, /en/privacy-policy) and are fully readable without JS. Partner agreement · Public offer · Privacy policy

  14. Docs
    Technical checklist, changelog and disclosure policy

    Published neutral criteria for evaluating a CPA network technically (each with Birinchi Shop's answer and an evidence link), this changelog with the API versioning policy, and a vulnerability disclosure policy. Technical checklist · Disclosure policy · security.txt

  15. MCP / AI
    MCP: 2026-07-28 protocol and tool examples

    The partner and shop MCP servers now also support MCP protocol 2026-07-28 (alongside 2025-11-25 and older — nothing changed for existing clients). Tool descriptions gained examples; the partner MCP server is version 1.2.0. mcp.json · guide.md

  16. Tracking
    Real-time panel (SSE)

    An open panel shows a new order, status change, balance change or notification within 1–2 seconds (Server-Sent Events). If the connection drops, the panel reconnects by itself; a 60-second refresh remains as a fallback. Technical capabilities

  17. Infrastructure
    Standby server and hourly backups

    A live copy of the database on a separate standby server (a few seconds behind); hourly encrypted database backups; files, code and settings copied to the standby server hourly; alerts on failure. Switching to the standby server is manual. Technical capabilities

  18. Infrastructure
    Independent uptime monitoring

    An external monitoring service checks the site, API and panel every 5 minutes; public status page at /status. /status · Technical metrics

  19. API affects /api/v1
    API /stats: days in Tashkent time

    Daily grouping (panel stats and API /stats with group_by=day) is now computed in Tashkent time. Previously some orders placed after midnight fell into the previous day. API docs

  20. Tracking affects /api/v1
    Click log; clicks and unique_clicks in API /stats

    Every click is logged: bots, link previews and prefetches are separated, unique clicks (30-minute window), CR by period; raw IPs are not stored. API /stats responses gained clicks and unique_clicks fields. "Tracking accuracy" measurement started. Technical metrics · API docs

  21. API affects /api/v1
    Open-order rule and double-submit guard

    For part of the catalog, a new order is refused while the customer's earlier order for that product is still in progress — the API returns 409 with code order_in_process. A simultaneous double submit creates one order. API docs · Technical metrics

  22. Docs
    Technical metrics and Technical capabilities pages

    Public technical metrics (API latency P50/P95, 5xx rate, postback delivery, duplicate rate, status freshness, payout speed) with the methodology and as JSON (/api/public/tech-metrics); all technical capabilities in a Yes / Partial / No table. Technical metrics · Technical capabilities

  23. Integration
    Meta Conversions API: Delivered event

    When an order is delivered, a separate Delivered event is sent to Meta (to the partner's dataset and landing/site pixel) so ads can be optimized for real sales. guide.md

  24. API affects /api/v1
    API: offer name and description in ru/en (?lang)

    GET /offers and GET /offers/{id} accept an optional lang=uz|ru|en parameter; Uzbek is returned when no translation exists. API docs

  25. API affects /api/v1
    API: smart offer search

    GET /offers?search= handles synonyms, typos, Cyrillic and Latin spelling; without sort, results are ordered by relevance. API docs

  26. Docs
    Public GitHub repo: API examples

    curl, Node.js, Python and PHP samples, webhook signature verification, a Keitaro postback guide, MCP setup and a copy of the OpenAPI spec. GitHub

  27. Integration
    Targenix integration

    Targenix leads arrive via webhook and become orders (matched by link ID or full link); order statuses are reported back to Targenix. Technical capabilities

  28. Security
    Data protection page

    How passwords, payout documents, customer phones, sessions and API keys are protected — on a public page. Data protection

  29. API affects /api/v1
    Self-order ban

    A partner cannot place an order to their own phone number: checked in the panel, API, AI chat and link form; the API returns 422 with code own_phone. API docs

  30. MCP / AI
    Shop MCP: interactive view

    The shop MCP server gained an interactive product view inside the AI chat (MCP Apps), with a separate ChatGPT variant. Shopping via AI

  31. MCP / AI
    MCP Registry and mcp.json

    The shop MCP server was published in the official MCP Registry (uz.birinchishop/shop); servers are listed in /.well-known/mcp.json. mcp.json

  32. Docs
    Guide for AI coding assistants

    /api/v1/guide.md — a single file generated from the live OpenAPI spec: hand it to Claude, ChatGPT or Cursor and ask it to write the integration. guide.md

  33. API affects /api/v1
    API: AI manager and Meta ads endpoints

    New scopes insights:read, ads:read, ads:write; /insights, /orders/{id}/sale-chance, /ads/*, /actions/{id}. Pausing ads is immediate; resuming or changing budgets returns 202 with pending_confirmation — the partner confirms. MCP gained prompts and resources. Spec version: 2026-10-23. API docs · OpenAPI

  34. MCP / AI
    Shop MCP server for shoppers

    /api/shop/mcp — no key needed: product search, product details, placing an order (only after the shopper's explicit consent) and order status. Shopping via AI

  35. Security
    AI connections via OAuth 2.1; /.well-known

    Claude.ai and ChatGPT connectors connect to the partner MCP server without a key via OAuth 2.1 (PKCE) — the partner approves the connection in the panel. /.well-known now serves OAuth metadata, mcp.json and security.txt. mcp.json · security.txt

  36. Security
    API keys: confirmation and automatic revocation

    Creating a key requires the password or a Telegram code; a password reset automatically revokes all API keys. Data protection

  37. API affects /api/v1
    Public API v1 launched

    REST API (offers, links, orders, stats, event feed), HMAC-signed JSON webhooks, S2S postbacks (with macros, up to 8 retries), click_id and sub1–sub5, Idempotency-Key, the partner MCP server and an OpenAPI spec. API docs · OpenAPI

The changelog lists technical changes partners can notice. Internal work and details of security fixes are not published.

API versioning policy

  • Major version in the path. There is one version today: /api/v1. Every response carries an X-API-Version: v1 header.
  • Spec date. info.version in the OpenAPI spec and the api_version field in webhook payloads show the spec revision date (currently 2026-10-23). Small additions do not always bump this date — the exact list is in this changelog.
  • Only additive changes within v1. New endpoints, optional parameters, new response fields, new event types or error codes. Since the 2026-10-22 launch no endpoint or field has been removed or renamed in v1.
  • What clients should do. Ignore unknown response fields and branch on error.code, not on the message text.
  • Breaking changes. Removing a field or endpoint, or changing a name or type, is not done within v1 — it would become a new major version announced in advance in this changelog. There are no plans for a v2 yet, so no specific deprecation period has been set.
  • Exception. Changes made for security or personal data protection (for example, masking a field value) may ship without notice. Business rules (the duplicate rule, order submission conditions) may also change — they surface as new error codes and are recorded here.
  • MCP. The MCP servers support several protocol versions at once (currently 2026-07-28, 2025-11-25 and older); the server version is in serverInfo.version.

Start today

Sign up, pick a product and get your first tracking link.

Become a partner

How to follow changes

FAQ

What is the current Birinchi Shop API version?

v1 (/api/v1, every response has X-API-Version: v1). The spec date is in the OpenAPI info.version and the webhook api_version field — currently 2026-10-23.

Will my integration break when API v1 changes?

Only additive changes are made within v1: new endpoints, optional parameters, new fields or error codes. Since 2026-10-22 no endpoint or field has been removed. Ignore unknown fields and branch on error.code.

What happens with a breaking change?

It is not made within v1 — it would ship as a new major version announced in advance in this changelog. There are no plans for a v2 yet.

What is not in the changelog?

Internal and administrative work and details of security fixes. Technical changes partners can notice — API, MCP, tracking, integrations, infrastructure — are recorded with a date.

Earn on every delivered order

Warehouse, call center and delivery are on us. You bring the traffic.

Sign up free

More in English

All English pages →