
OOO "DALWEBSTROY"
Dwstroy: Authorization via Telegram
The Dwstroy: Telegram Authorization module extends the capabilities of standard authorization via the Telegram messenger.
Аккаунт в General iT
Войдите или создайте аккаунт для управления услугами в панели.

MODULE FOR 1C-BITRIX
Kokhanenko: B2B Catalog API
The Kokhanenko: B2B Catalog API module adds a managed API to 1C-Bitrix sites for exporting catalogs to external systems: dealer portals, partner showrooms, mobile applications, CRM, PIM, BI reports, and integration services.
The Kokhanenko: B2B Catalog API module adds a managed API to 1C-Bitrix sites for exporting catalogs to external systems: dealer portals, partner showrooms, mobile applications, CRM, PIM, BI reports, and integration services.
The module is designed not for mass price list export, but for securely providing catalog data to external systems, partners, dealers, and client applications via a protected API with individual tokens and access restrictions.
The solution allows providing different data sets to different clients rather than the entire catalog to everyone. A separate API token can be created for each external client; tokens can be grouped, and restrictions can be configured for response fields, price types, catalog sections, and product property values.
The API returns products, active sections, and the count of available items. It supports JSON and XML formats, pagination, Bearer authorization, file download of responses, and a public HTML page /api/ with a brief guide to the endpoints.
This solution is suitable for online stores and B2B portals on 1C-Bitrix, as well as companies that distribute catalogs to dealers, partners, or franchisees.
The Kokhanenko: B2B Catalog API module is designed for integrating external websites, mobile applications, CRM, PIM, and BI systems with a product catalog. It enables teams to manage access rights to prices, stock levels, product properties, and catalog sections independently.
Key features include product endpoints at /api/v1/products, /api/v1/products.json, and /api/v1/products.xml, as well as a product count endpoint at /api/v1/products/count supporting both JSON and XML formats. The categories endpoint /api/v1/categories is available with JSON and XML support.
Authentication is handled via the Authorization: Bearer header. Legacy compatibility is maintained through the query parameter token. The system supports token groups and individual rules for specific tokens.
The API allows limiting response fields, restricting available price types, excluding specific sections from results, and filtering products by property values. Access Control Lists (ACL) are applied before pagination, ensuring consistent counting of the available product set across /products and /products/count endpoints.
Additional capabilities include selecting specific infoblock properties for external exposure, basic export of trade offers, prices, and stock levels. The API request log is maintained without storing full tokens or query strings. Successful responses include service fields api_version: v1 and schema_version: 1.0.
Security
The module does not store full plain tokens in the database. The complete token value is displayed only once during creation or reissue; thereafter, administrative lists show only the prefix. For production integrations, Bearer authorization is recommended to prevent tokens from appearing in URLs, access logs, or browser history. The request log records the endpoint, method, status, duration, IP address, token or user ID, and a hash of the query string. Full tokens and original query strings are not written to the log.
General iT can install and configure this module and check how it works on your website.
UPDATE HISTORY
In the module settings, buttons have been added to automatically connect the module's route file in /bitrix/.settings.php and to add a rewrite rule for /api/v1 in .htaccess if a check reveals an error.
Before modifying system files, a backup is created next to the original file with the suffix .kokhanenko_catalogapi_YYYYmmdd_HHMMSS.bak.
Automatic actions only add missing settings or rules and do not remove existing project configurations.
After a successful fix, the path to the created backup is displayed in the settings, and the fix button is hidden.
The ability to specify an individual list of product properties for a token group or a specific token has been added.
The priority for selecting API output properties is implemented as follows: token → group → general module settings → no properties are returned.
An empty individual list is considered as the absence of individual settings and includes inheritance from the next level.
A separate block titled 'Product Properties for API Output' has been added to the administrative pages for group and token restrictions.
The API response format, endpoints, and schema_version remain unchanged.
YOUR PROJECT INFRASTRUCTURE
BEFORE YOU ORDER