Publishing an Application in the Bitrix24 Marketplace

You have developed an application for Bitrix24, but the process of publishing in the marketplace turned out to be more complex than the code. Partner registration, card design, technical moderation—each stage can take weeks. Our experience shows that without preparation, the first attempt rarely passes on the first try. We have helped dozens of projects get through moderation—from simple integrations to complex subscription services. For example, a task management app integrating Bitrix24 and Trello passed moderation only on the third attempt due to incorrect OAuth token handling. We fixed the logic and got approval within two weeks.

Publishing in the Bitrix24 marketplace is a separate project because moderation requirements are constantly changing. Recently, OAuth scope checks have been tightened: extra permissions mean automatic rejection. Handling 429 Too Many Requests is a typical reason for rejection. We have systematized common errors and use a 50+ point checklist. As a result, the average time to pass moderation is reduced by 3 weeks, and budget savings from avoiding rework reach up to 100,000 rubles. A typical integration project costs between 100,000 and 200,000 rubles, so these savings are significant.

Our Approach and Key Solutions

We address compliance with moderation requirements, design a card that sells, and set up billing and subscriptions. Specifically:

• Compliance: We check security, correct API operation, and UX. We remove unnecessary scopes, configure error handling, and ensure Russian language support.
• Card design: We prepare screenshots (1280×800 PNG), an icon (128×128 with transparency), a short description up to 160 characters, and a full description with formatting. We avoid typical mistakes like test data on screenshots or using the Bitrix24 logo without permission.
• Billing: For paid applications, we connect the 1C-Bitrix system. For subscriptions, we implement onAppPaymentAdd and onAppPaymentDelete event handling.

We use PHP 8.2+, Bitrix24 REST API, and custom components. Example: a logistics app integrating CDEK. The main challenge was correctly handling subscription cancellation via the onAppPaymentDelete event. We implemented automatic feature deactivation without deleting user data, and the app passed moderation on the first try. Another example: a customer support chatbot rejected due to missing CSRF protection. After adding tokens and verifying the request source, moderation was successful.

Preparation and Process

Before submission, ensure your app meets basic requirements. Use the official REST API Bitrix24 documentation. Verify that all API requests handle errors 401 (re-auth) and 429 (backoff with exponential delay). Make sure there are no placeholder screenshots and the icon does not violate trademarks. We include two moderation iterations in our service, covering 90% of cases.

Our work process:

1. Analysis – study your app's API and check scopes.
2. Card preparation – write descriptions and prepare media.
3. Technical preparation – configure HTTPS, error handling, and sandbox.
4. Submission for moderation – go through all stages.
5. Rework based on feedback – up to two iterations if needed.
6. Publication and monitoring.

Estimated timelines: 2 to 6 weeks depending on complexity and number of iterations. On average, our clients get approved 3 weeks faster than typical due to our preliminary audit.

What's Included in Our Service

• Compliance checklist (over 50 items)
• Card design: title, description, screenshots, icon
• OAuth/scope configuration and event handlers
• Testing on a sandbox portal
• Moderation submission and up to two rounds of rework
• Monetization consultation (model selection, billing setup)
• One month post-publication support

Moderation and Handling Rejection

The moderator tests the app in a test environment, checking security (no access_token in GET, CSRF protection, XSS prevention), correct API operation (handling 401 and 429), and UX (meaningful loading states, errors shown on screen, mobile functionality). Apps that do not handle 429 are rejected in 80% of cases, while those with correct backoff get approved on the first try. Rework costs can reach 30,000–50,000 rubles per iteration.

If rejected, analyze the reason: scopes, description mismatch, or technical errors. Usually, fixing the issues and resubmitting suffices. Our service includes two moderation iterations.

Monetization Models

Common Mistakes in Moderation

Why Choose Us

We have over 5 years of Bitrix24 experience and more than 30 integrations and applications. Our solutions get approved without rejection, with an average publication time of 3 weeks. We rely on the OAuth standard and the official Bitrix24 REST API guide. If you want to speed up the process and avoid typical mistakes, contact us for an audit and preparation. Get a consultation right now to assess your solution's readiness.