🔗 Ready Boostore Integration on GitHub — API-commerce Script
API-commerce is a ready-made open-source PHP script that allows you to manage your website content on Boostore.pro via a convenient REST API. Launch it in 5 minutes on your local computer via OpenServer or Apache and automate work with products, articles, visual blocks and site pages.
📄 Table of Contents
🚀 1. What is API-commerce and why you need it
API-commerce is an open-source PHP script published on GitHub in the repository BooStore-pro/API-commerce. It acts as an intermediary between your local environment and your website on Boostore.pro, providing a convenient REST API for content management.
The script allows you to perform virtually all operations available in the Boostore.pro admin panel, but via HTTP requests — this opens up wide possibilities for automation, integration with CRM, warehouse systems, content generators (ChatGPT, neural networks) and any external services.
⚙ What can the script do?
📦 Products
Create, edit, delete products. Manage prices, stock, attributes, images, categories. Bulk import and update.
📝 Articles
Publish articles to the blog. Manage meta tags (title, description, keywords), blog categories, language versions. Full control of HTML content.
🗄 Visual Blocks
Create and edit blocks for building websites: headers, footers, product sections, banners, galleries — everything that pages on Boostore.pro are built from.
📄 Site Pages
Manage pages: home, catalog, contacts, about us, landing pages. Full control of HTML, blocks, SEO parameters.
⚙ 2. Installation and launch of the script via OpenServer / Apache + PHP
The script is written in pure PHP 7.4+ and does not require complex setup. All you need is an Apache web server with PHP and curl support. Let's look at installation using OpenServer — the most popular tool among web developers.
👉 Step-by-step installation on OpenServer
Download the repository from GitHub
Go to github.com/BooStore-pro/API-commerce and download the ZIP archive or clone the repository via Git:
Place the script in the OpenServer domain folder
Extract the archive to the OpenServer/domains/api-commerce.local/ folder or any other folder of your local domain.
Configure the settings via web interface
After the first launch, open the script in your browser — you will be taken to the configuration page with a convenient GUI. Below is a detailed description of all parameters.
mod_rewrite module and the curl extension are required.
📦 3. Which sections are available for management via API on GitHub
API-commerce provides endpoints for all key sections of Boostore.pro. Each endpoint supports standard CRUD operations (Create, Read, Update, Delete) via HTTP methods: GET, POST, PUT, DELETE.
🗃 Complete list of available sections
| Section | API Methods | Description |
|---|---|---|
| Articles / Blog | GET, POST, PUT, DELETE | Full article management: titles, HTML content, meta tags, blog categories, language versions, publication status |
| Pages | GET, POST, PUT, DELETE | Site page management: home, catalog, contacts, landing pages. Full HTML access, SEO parameters, block binding |
| Visual Blocks (Blocks/Menus) | GET, POST, PUT, DELETE | Create and edit blocks for page assembly: HTML blocks, product blocks, menus, banners, galleries, carousels — any elements of the Boostore.pro visual editor |
| Store Categories | GET, POST, PUT, DELETE | Create and edit product categories, subcategories, nesting, sorting |
| Manufacturers | GET, POST, PUT, DELETE | Manage brand manufacturers: create, edit, link to products |
| Collections | GET, POST, PUT, DELETE | Manage product collections: create, edit, sort, populate |
| Products | GET, POST, PUT, DELETE | Full product management: create, edit, delete. Prices, stock, attributes, images, categories, bulk operations |
📈 4. Parameter flexibility
One of the main advantages of API-commerce is its flexible settings system. The script allows you to fine-tune the import and export of articles via the web configuration interface. All parameters are available immediately after installation — without editing PHP files.
📋 General Settings
Basic parameters that determine the connection to the site and content filtering:
| Parameter | Description | Default Value |
|---|---|---|
| 🔑 Access Key (Consumer Secret) | API key for authorization on the Boostore.pro website. Created in the admin panel: "Settings → API" | — required |
| 🌐 Site URL | URL of your site on Boostore.pro, e.g. https://mysite.boostore.pro | — required |
| 📂 Allowed Categories | IDs of blog categories the script works with. Empty — all categories | all categories |
| 🌐 Reference Article Language | Articles in this language are considered the reference. When retrieving articles in other languages, fields are compared and synchronized with the reference | Russian (ru) |
📥 Import Filters (retrieving articles from the site)
Parameters that affect the download of articles from the site to local HTML files. Allow you to fetch only the needed articles for a specific period:
| Filter / Parameter | Description | Default Value |
|---|---|---|
| 📥 Articles per request (per_page) | Number of articles loaded per 1 API request. Maximum 2000 | 200 |
| 📅 Date from | Load only articles with publication date not earlier than specified (format: dd.mm.yyyy) | — not set |
| 📅 Date to | Load only articles with publication date not later than specified (format: dd.mm.yyyy) | — not set |
| 🌐 Language | Filter by article language. You can select a specific language or "all" | all |
| 🆔 ID > | Load only articles with ID greater than the specified value | 1000 |
| 🆔 ID < | Load only articles with ID less than the specified value | 5000 |
| 🔍 Search by name (slug) | Search articles by part of slug/name. For example: shoes — will find all articles with the word shoes in the URL | — not set |
| 📂 Categories for filtering | List of category IDs from which to load articles. If none are selected, all categories are processed. Multiple can be specified | all categories |
📁 Additional structure options for import
- Separate planned into blog/planned/ — articles with a scheduled publication date are saved to a separate
blog/planned/folder - Separate by category folders — each blog category creates its own subfolder, the file structure mirrors the rubric structure
- Only with name (skip without name) — if an article has no slug/name, it is skipped during import
🔄 Reference correction
After saving articles, the script can automatically synchronize certain fields with the reference article (by slug):
- multilangid — multilingual group identifier
- planned — publication date
- status — publication status (0/1)
- datestamp — creation/modification date
📤 Export Filters (sending articles to the site)
Parameters that control the publication of local HTML files on the Boostore.pro website:
| Parameter | Description | Default Value |
|---|---|---|
| 🔄 Export Mode | Determines the behavior when sending: "Add + Update" — creates new and updates existing articles; "Add new only" — skips existing ones; "Update existing only" — does not create new ones | Add + Update |
| 📦 Send Limit | How many articles can be sent in one run. Maximum 5000 | 200 |
| 📅 Publication Date Mode | How to determine the date: from each article's meta data or forcibly for all | From meta data (date from each article) |
| 📅 Override planned | If a date is set, it will be applied to ALL articles during export. Empty — use from meta data | — not set (from meta data) |
| 🔒 Access Status (status) | Publication status determination mode: from each article's meta data or forcibly 0/1 for all | From meta data (status from each article) |
| 🔄 Reference correction | Which fields to automatically correct by reference article when sending: multilangid, planned, status, datestamp | multilangid, planned, status, datestamp |
📅 Date Management Parameters
API-commerce gives you full control over publication dates both during import and export:
| Mode | Parameter | How it works |
|---|---|---|
| 📥 Import (filter) | "Date from" / "Date to" | Load only articles within a date range. Convenient for incremental import — for example, fetch everything from the last week |
| 📥 Import (structure) | "Separate planned" | Articles with a future publication date are saved to blog/planned/ rather than the main folder. Drafts are not mixed with published content |
| 📤 Export (mode) | "Publication Date Mode" | "From meta data" — each article is published with its own date. If "Forced" is selected, all articles receive one specified date |
| 📤 Export (override) | "Override planned" | Allows you to bulk-set a publication date for all sent articles. For example, to schedule publication for tomorrow |
| 🔄 Synchronization | "Reference correction: planned, datestamp" | When synchronizing multilingual articles, the dates of the reference (usually Russian) version are copied to other languages. All versions of an article are published simultaneously |
sitecreate_en category, published in July 2026, with IDs from 15000 to 16000. Set the filters: language = ru, category = 1418, date from = 01.07.2026, date to = 31.07.2026, ID > 15000, ID < 16000. The script will load only the needed articles — no garbage.
📝 5. Full access to HTML content
One of the strong points of API-commerce is the ability to pass arbitrary HTML content in virtually any field: product description, article body, visual block content, page content. No restrictions on tags and attributes.
📄 Where HTML can be used
📦 Products
Full product description with specification tables, packing list, video reviews, nested images — any HTML in the description field.
📝 Articles
Full-fledged blog articles: H1-H6 headings, images, tables, lists, quotes, code blocks, Schema.org markup — everything HTML supports.
🗄 Blocks
Visual blocks for building pages: banners, galleries, carousels, forms, videos, animations — any HTML/CSS constructs supported by the browser.
📄 Pages
Full control over page content: home, about us, contacts, promotional landing pages — HTML, CSS (via inline styles or external file includes), JavaScript.
📝 Example: Article HTML content with image and list
On the site, this HTML will be correctly displayed with headings, images, lists and links — like a full-fledged blog article.
🔄 6. Multilingual — content management in all languages
Boostore.pro supports multilingual websites out of the box. API-commerce fully works with this functionality — you can create and edit content in any supported language of the site through a single API.
🔄 How multilingual works in API-commerce
Each object (product, article, block, page) can have multiple language versions. When creating or updating via API, you specify the language parameter — the script automatically creates or updates the corresponding language version.
✅ Supported languages
API-commerce supports all languages available in your Boostore.pro installation: Russian (ru), Ukrainian (ua), Polish (pl), English (en) and others. The language parameter accepts the two-letter ISO 639-1 language code.
multilangid parameter links different language versions of the same object. This allows you to manage an entire multilingual website through API-commerce — create, update and synchronize content in all languages within a single script or cron job.
❓ Frequently Asked Questions about API-commerce
Answers to the most popular questions about installing, configuring and using the API-commerce script for integration with Boostore.pro.
Is it difficult to install API-commerce without programming experience?
Installation does not require programming skills. Just download the archive from GitHub, extract it to the OpenServer folder and enter API keys via the script's web interface. The whole process takes 5-10 minutes. To make API requests, you can use any HTTP client: Postman, Insomnia, curl or ready-made scripts from the documentation.
Can the script be run on a hosting server instead of a local PC?
Yes. The script works on any hosting with Apache + PHP 7.4+ and curl. You can place it on a separate subdomain or in a separate folder of your main domain. However, for security reasons, it is recommended to run the script on a local computer or in an isolated environment, not in public access.
What data is needed to connect to Boostore.pro?
You will need: the URL of your site on Boostore.pro and an API key (created in the admin panel under "Settings → API"). Keys can be of different types — read-only or full access to all operations with a single key.
Are there any limits on the number of API requests?
The script has no built-in limits on the number of requests. Limits may be set at the hosting or Boostore.pro plan level. For bulk operations (importing thousands of products), it is recommended to use pauses between requests — the script supports asynchronous queues for this.
Can API-commerce be used for automatic import of products from CRM or 1C?
Yes, this is one of the main use cases. You can set up data export from CRM/1C in JSON or CSV format, and the API-commerce script will process this data and create/update products on the site. The script supports bulk creation, update by SKU, stock and price management. Integration is configured via HTTP requests from your CRM.
How is security ensured when working via API?
API-commerce uses API keys for authentication of all requests. It is recommended to place the script on a local computer or in a closed subnet, not in public access. All requests to Boostore.pro are made via HTTPS. For additional security, you can configure IP filtering and restrict access to the script via the .htaccess file.
Is the script free? Are there any hidden fees?
API-commerce is a completely free open-source script (MIT license). You can download, install and use it without any restrictions or hidden fees. The source code is available on GitHub for studying, modification and adaptation to your needs.
Which PHP versions are supported?
The script works on PHP 7.4, 8.0, 8.1, 8.2 and 8.3. PHP 8.1+ is recommended for maximum performance. The curl and json extensions are required — they are included in the standard PHP distribution.
Where to ask questions and report bugs?
All questions, suggestions and bug reports are accepted via GitHub Issues of the repository. You can also leave your feedback or suggest improvements there. The developer actively maintains the project and responds to community questions.