A developer spent a month integrating with Bitrix24, but got rejected at moderation due to extra scopes. Statistics: 80% of apps fail certification on the first try. Marketplace certification checks 30+ criteria. Any can cause refusal. We help you pass on the first attempt, saving time and resources.
Our track record: over 20 certified projects, 5 years working with the Bitrix24 ecosystem. We've developed a methodology that reduces review iterations by 2–3 times. You get a ready-to-publish app without unnecessary delays.
How to Avoid Common Certification Mistakes
Preparation starts with a code audit against the official checklist. Verify the OAuth flow: handle installation, uninstallation, token refresh. Ensure requested scopes (crm, tasks, disk) are actually used. Each extra scope is a risk. Tokens must never be passed in GET parameters or localStorage. Use only POST or the Authorization header. HTTPS is mandatory for all resources.
We also check API error resilience. The app should not crash with a white screen when permissions are missing. Instead of a 403, return a clear UI response. Rate limiting matters too. Avoid loops without delays. Use caching and pagination. According to the documentation, the app.info method helps handle missing modules.
What Does the Bitrix24 Team Check?
Technical criteria: correct OAuth flow, scope–functionality match, token transmission security, API error handling, rate limit resilience.
Content criteria: description must match functionality. Screenshots must reflect the real interface. Localization in Russian, no machine translation. Icon 128×128 px. Do not use 1C-Bitrix logos.
Why App Might Fail Moderation?
Common reasons include requesting unnecessary scopes, crashing without required modules, passing tokens in GET, screenshots with test data, missing uninstall handling, and incompatibility with mobile portals. We find and fix these during audit. For example, if the app requests crm scope unnecessarily, we remove it. If no uninstall handler exists, we implement /uninstall with data cleanup. If screenshots contain test data, we remake them with realistic demo data.
How to Speed Up the Review?
Attach a test portal with demo data. Write a testing guide. Test the app in incognito mode. Ensure all external services are stable. These measures cut review rounds from 3–4 to 1–2.
How We Help You Pass Certification
We handle all preparation and support. Our approach gets your app certified on average 40% faster than doing it yourself.
- Code audit against developer documentation requirements.
- Fix critical errors: scopes, OAuth, security.
- Prepare documentation: description, screenshots, privacy policy.
- Set up test portals with different tariff plans.
- Support during review: analyze comments, fix, resubmit.
- Final check before submission.
Case in point: A client saved 2–3 weeks because we pre-prepared test accounts and a testing guide. The reviewer immediately saw a working scenario. Review rounds dropped from 4 to 1–2.
Process
- Analyze current app state — code and content audit.
- Fix critical errors: scopes, OAuth, security.
- Prepare documents and screenshots.
- Set up test portals and sandbox testing.
- Submit for moderation from the partner cabinet.
- Support during review: quick response to comments.
- App publication.
Timeline
| Stage | Time |
|---|---|
| Audit and fixes | 1–3 weeks |
| Initial review | 1–2 weeks |
| Iterations (1–2 rounds) | 1–3 weeks |
| Total from ready app to publication | 3–8 weeks |
Time depends on app complexity and iteration count. We minimize delays through thorough preparation.
After Certification
Once status is "Approved", you can publish updates. Each new version undergoes a shortened review if scopes, monetization model, and documentation remain unchanged. Major changes require a full cycle.
Get a consultation on preparing your app for certification. Contact us for an audit before submission. We guarantee passing moderation on the first try if you follow our recommendations.