Setting up Bitrix24 Market

Configuring Bitrix24 Market

Bitrix24 Market is a catalog of applications and integrations available from any portal via the Applications menu. If your department connects telephony, email, or a corporate messenger through the Market, setup takes as little as 5 minutes. If you need to publish your own application or manage installed ones — there are nuances.

Installing applications from the Market

Path: Applications → Market. Applications are organized by category: CRM, Telephony, Tasks, Service Integrations, etc.

When installing an application from the Market:

1. OAuth authorization: the application requests permissions for the required scopes
2. The user confirms the permissions
3. The application registers its placements, event handlers, and menu items

After installation the application appears in Applications → My Applications. Management is done from there only.

Managing installed applications

List of installed applications with permissions and status:

/devops/section/api/apps/

Here you can also see: which scopes the application requested, which webhooks it registered, and the date of last activity. This is useful for security audits — forgotten test applications with administrator permissions are sometimes discovered.

Removing an application via REST:

POST /rest/app.uninstall
{
  "clear": 1
}

The clear=1 parameter deletes all application data from the portal (settings, options, placements). Without it the application is deauthorized but the data remains — convenient for reinstallation without losing configuration.

Configuring applications after installation

Many Market applications require configuration after installation: entering API keys of third-party services, setting up field mapping, choosing responsible employees. The configuration interface opens from the application card.

If an application uses app.option.set/app.option.get to store settings:

POST /rest/app.option.set
{
  "options": {
    "api_key": "your-service-api-key",
    "sync_interval": "60",
    "deal_stage_mapping": "{\"WON\":\"DELIVERED\"}"
  }
}

Settings are stored in the b_app_option table on the portal, tied to the application's member_id.

Updating permissions of an installed application

If a developer adds a new scope, the portal administrator will receive a notification offering to update the permissions. To manually check for updates:

Applications → My Applications → [application] → Check for Updates

When updating permissions the user goes through OAuth confirmation again. There is no automatic update without user involvement — this is a platform security restriction.

Publishing your own application to the Market

Requirements for publication:

• Partner registration at partners.1c-bitrix.ru
• HTTPS for all application endpoints
• A correct manifest with description, screenshots, and icon
• Passing technical review by the Bitrix team

Typical reasons for rejection during review:

• Handler URL is unavailable or returns an error
• Application requests unnecessary scopes (requests disk and calendar but uses only crm)
• Description in Russian is missing
• No proper handling of uninstallation (OnAppUninstall)

Review timelines: 3 to 14 business days depending on the Bitrix team's workload and the complexity of the application.