Publishing an Application in Bitrix24 Marketplace
Submitting an app to Bitrix24 marketplace — separate task taking 2 to 8 weeks, often stumbling on moderation requirements. Multi-stage process: first partner registration, then app card setup, then technical check, then editorial review. Each stage can result in rejection with wording you'll have to decipher.
Preliminary Requirements
Before submitting application, must meet several requirements:
Partner status. Only companies registered in 1C-Bitrix partner program can publish apps. Registration via partner.1c-bitrix.ru, basic status — "Partner". Without this, publish form in developer account unavailable.
App must be registered in developer account on bitrix24.ru/apps/. On registration specify client_id, client_secret, OAuth scope list, and redirect URI. After registration app assigned numeric application_id.
Technical readiness:
- HTTPS with valid certificate on all endpoints
- App works in sandbox portal without errors
- All declared scopes really used (extra scopes — rejection reason)
- Error handling: app doesn't fall on tariffs without needed modules
- Russian language support in interface mandatory
App Card Setup
Card in marketplace — what user sees before install. Content requirements:
Mandatory elements:
- Name (up to 60 characters), brief description (up to 160 characters)
- Full description with formatting — editor in account
- Screenshots: minimum 3, PNG/JPG format, 1280×800 pixels
- Icon: 128×128 pixels, PNG with transparent background
- Promo video — optional, but increases install conversion
- App category (CRM, tasks, communications etc.)
Common rejection reasons at setup stage:
- Screenshots with test data or placeholder text
- Russian description poor quality or copied from elsewhere
- Icon with Bitrix24 logo or 1C brand colors without permission
- Declared functionality doesn't match what app actually does
Technical Moderation Requirements
Most opaque part of process. Moderation team checks app manually in test environment. Checks:
Security:
- App doesn't request user data not needed for operation
- No
access_tokentransmission in GET URL parameters (logged at proxy) - CSRF protection on all forms
- XSS protection outputting Bitrix24 data in own interface
API Correctness:
- Proper
401 Unauthorizedhandling — app initiates re-auth, doesn't fall - Rate limit handling (
429 Too Many Requests) — retry with exponential backoff - App doesn't call
event.bindin loop on each iframe open — only on install
UX:
- App shows meaningful loading state, not blank screen
- Errors displayed to user, not just console
- App minimally functional on Bitrix24 mobile version
Publication Process: Steps and Timeline
| Stage | Action | Typical Timeline |
|---|---|---|
| Partner registration | Submit application, document verification | 3–7 days |
| App registration | Fill form, get client_id | 1–2 days |
| Card preparation | Screenshots, description, icon | 3–5 days |
| Technical testing | Self-check by checklist | 2–5 days |
| Initial moderation | Automated checks | 1–3 days |
| Editorial review | Manual check | 5–14 days |
| Revision iterations | Fixes + re-submission | 3–10 days |
| Publication | Appears in catalog | 1–2 days |
Realistic total timeline from ready app to publication — 3–6 weeks on first iteration.
Publication Types and Monetization
Marketplace offers models:
- Free — app installs without payment. Monetization inside app via own billing.
- Paid (one-time) — user pays once on install via 1C-Bitrix system. Marketplace commission percentage of sale.
- Subscription — monthly/yearly payment via Bitrix24 billing. App receives notifications on renewal/cancellation via events.
- Freemium — basic functionality free, advanced — paid. Most popular model.
For subscription model app must handle events onAppPaymentAdd (payment passed) and onAppPaymentDelete (subscription canceled/expired) and enable/disable functionality accordingly.
After Publication
Publication — not end. Bitrix24 periodically updates API and deprecated methods really shut down. Must subscribe to developer changelog and monitor BITRIX24_PHP_SDK versions.
App rating in marketplace affects its position in catalog. First reviews critical — worth working on onboarding so user can start using app in 5 minutes without reading instructions.
App updates (new versions) undergo repeat moderation, but faster — usually 3–7 days if changes don't affect requested scopes and don't change monetization model.