Postman Collection Setup for 1C-Bitrix API

Why a Postman Collection Is Essential for Bitrix API

A CusDev developer deals with dozens of endpoints—1C product exchange, lead creation, order processing. Without pre-built requests, every test turns into copying cURL from the docs. We set up Postman collections so that one click and the API responds. Our Bitrix experience: over 10 years, 50+ projects, quality guarantee.

A Postman collection for 1C-Bitrix is not just a set of HTTP requests; it's a full automation tool for testing and documenting the API. It includes automatic authorization, environment variables for different stages, and tests for status and response structure. With such a collection, regression testing of 20 endpoints takes 1–2 minutes instead of 30–60 minutes of manual work. Time savings per cycle: up to 20 hours per month.

Problems the Collection Solves

• Missing documentation. Bitrix developers often rely on verbal agreements. The collection becomes a single source of truth.
• Authorization errors. JWT tokens expire, API keys get mixed up. Automation via Pre-request Script eliminates human error.
• Long regression. After every update you need to check all endpoints. Collection Runner and Newman do it in minutes.

How to Automate Authorization in Postman

When working with JWT authorization, the token must be obtained and inserted into each request. In Postman this is solved via a Pre-request Script in the login request:

pm.sendRequest({
    url: pm.environment.get('base_url') + '/api/v1/auth/login',
    method: 'POST',
    header: { 'Content-Type': 'application/json' },
    body: {
        mode: 'raw',
        raw: JSON.stringify({
            login: pm.environment.get('api_login'),
            password: pm.environment.get('api_password')
        })
    }
}, function(err, res) {
    if (!err) {
        pm.environment.set('token', res.json().token);
    }
});

For other requests, in the Authorization section select Bearer Token and use {{token}}. Or set authorization at the collection level—then all requests inherit it. This reduces setup time per request from 5 minutes to 10 seconds—30x faster.

What Is Included in the Collection Setup

• Designing the collection structure (endpoint groups: Auth, Catalog, Orders, CRM)
• Creating environment variables for dev/stage/prod
• Configuring Pre-request Script for automatic authorization
• Adding tests for each request (status, response structure, required fields)
• Exporting the collection in JSON (Collection v2.1) and integration with Git
• Documentation on running (including Newman for CI/CD)
• Team training (1 hour online)

How We Set Up the Collection: Process

1. API analysis. Study the endpoints, methods, authorization, data formats.
2. Structure design. Break into logical groups, create folders.
3. Environment creation. Prepare variables for each stage.
4. Request implementation. Add headers, bodies, parameters.
5. Authorization automation. Write Pre-request Script.
6. Tests. Add checks for each request.
7. Export and integration. Save to repository, set up Newman in CI/CD.

Collection Runner and Newman

Collection Runner lets you run all requests sequentially and see if all tests pass. This is basic smoke testing for the API.

Newman is a CLI tool for running collections from the command line. It integrates into CI/CD:

npm install -g newman
newman run bitrix-api.postman_collection.json \
    -e production.postman_environment.json \
    --reporters cli,html

After each deploy, CI automatically runs the collection and checks API health. Time savings on regression: up to 20 hours per month.

How to Avoid Common Setup Mistakes

One frequent issue is improper storage of sensitive data. Never put logins and passwords in the collection itself. Use environment variables that don't end up in Git. Another mistake is forgetting to update the collection after API changes. We recommend storing the JSON collection file in the same repository as the code and updating it within the same task.

Documentation from the Collection

Postman automatically generates documentation from the collection: description of each request, example responses, parameters. It's not a full OpenAPI spec, but sufficient for internal use.

Why Invest in Collection Setup?

Setting up a collection for an API with 15–20 endpoints, including tests and environments, takes 1–2 days. Contact us for a consultation—we'll assess your project in one day. Order Postman collection setup and forget manual testing. Get a consultation via the form on our website—we'll respond within a business day.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.