The OPOTOPO module settings page in the 1C-Bitrix admin no longer fails with a «Class not found» error, and the site background jobs no longer log it.
A request with a revoked key is rejected right after the revocation, with no delay.
The API reference page shows the operations and webhook events instead of a blank screen.
A Seller API catalog sync item passes its own shop category as level names from the root instead of a platform category: the item lands in the category set by the shop category mapping, the same one files and feeds use; a new shop category appears in the mapping list of the developers section, and an item of an unmapped category is rejected with its path. The row categories operation returns each item's category without writing listings, so the client uploads the item's files to it.
A Seller API catalog sync item passes the product package: weight in grams, length, width and height in centimetres and the packaging kind, so a product from your site ships with the platform delivery service. An item without a package keeps the previous one. The PHP and TypeScript clients take the package from mapping paths and round fractions up.
An open-source WordPress plugin uploads a WooCommerce store catalog to the platform with no code: products, variations, stock, weight and dimensions on every change and hourly, store categories mapped in the "Store categories" card of the "API" section. Platform orders arrive as WooCommerce orders and are fulfilled from the "OPOTOPO" panel of the order screen: own delivery with a tracking number, handover to the platform carrier with places, ready for pickup, cancellation and shipment documents.
An open-source 1C-Bitrix module uploads an online store catalog to the platform with no code: products, SKU offers, stock, weight and dimensions on every change and hourly, store categories mapped in the "Store categories" card of the "API" section. Platform orders arrive as paid site orders and are fulfilled from the "OPOTOPO" block of the order form: own delivery with a tracking number, handover to the platform carrier with places, ready for pickup, cancellation and shipment documents.
A long webhook event name in its heading and a long field type in a schema description wrap instead of being cut off, and the reference page fits the screen width.
A seller's system reads its orders with a Seller API key, hands them over by its own delivery, a platform carrier or for pickup, cancels them and gets the shipment document; an order status change notification arrives at the chosen webhook. The @opotopo/seller-api npm package uploads a site catalog on Node.js with no third-party dependencies: it maps your records to marketplace items, withdraws items that dropped out of the catalog and reports rejections by SKU. The PHP, TypeScript and Laravel clients handle orders; the guides are in the "For developers" section of the knowledge base.
The opotopo/seller-api Composer package uploads a site catalog on any PHP framework, uploads files, withdraws items that dropped out of the catalog, receives purchase notifications and hands the buyer a key from your own licensing system; opotopo/seller-api-laravel does the same from Eloquent models with a Laravel command and schedule. The guides are in the "For developers" section of the knowledge base.
A confirmed brand owner submits models in a batch with a key holding the "Manage brand models" permission: a model is found by barcode, manufacturer code or name, otherwise created, attributes and photos come in the same row, and publication is a batch flag. A row does not overwrite values set by a platform editor, and the response comes per row.
An external system submits items in a batch: the article number tells a new item from an existing one, and a repeated submission updates the listing instead of duplicating it. The platform fetches images by their links itself, the response comes per item, and the publish flag sends what was created straight to review.
A site that already serves its catalogue as a file needs no submission code: the integrations section takes the address and the update interval. The platform fetches the file on schedule, applies it by the same rules and withdraws items that disappeared from it.
The integrations section now holds a guide: the path from a key to the first synchronization, mapping your catalogue onto platform categories, behaviour on errors and rate limits, and ready-made call examples.
The replacement is the referral link from the referral code response.
The file goes through the common upload and the import takes its identifier.