Skip to Main Content
Tech Titan

Decision Guide

Webhook or OAuth app: choosing your integration's front door.

In short

Inbound webhook or OAuth local app for your Bitrix24 integration? Security, scopes, token lifecycle, events, and UI — compared with clear recommendations.

Every Bitrix24 integration authenticates one of two ways: an inbound webhook (a URL with an embedded key) or an OAuth application (tokens, refresh, scopes). The right choice is mostly about who runs the integration, how long it lives, and whether it needs UI.

By Saubhagya Srivastava, Founder & CEO, with the Tech Titan engineering teamBitrix24 Gold PartnerPublished Last updated

Webhook vs OAuth App at a Glance

Inbound WebhookOAuth (Local) App
Setup TimeMinutesHours to days
AuthenticationSecret URL tied to one userOAuth 2.0 tokens with refresh
Acts AsThe user who created itThe application, installed on the portal
PermissionsScopes chosen at creationScopes declared by the app
Interface Inside Bitrix24NoneCan add placements, tabs, and widgets
EventsOutbound webhooks for eventsEvent handlers bound by the app
Best ForServer-to-server feeds on one portalIntegrations that need UI or run on many portals

Inbound Webhooks: Fast, Simple, Powerful and Blunt

  • Created in minutes; no OAuth dance; perfect for server-to-server flows you control
  • The URL is the credential: leak it and someone has your scopes until you rotate
  • Tied to the creating user: their permissions, and death on their deactivation — create under a service account, always
  • No embedded UI, no app-level event subscriptions

OAuth (Local) Apps: More Machinery, More Control

  • Access + refresh token lifecycle — short-lived credentials instead of a standing secret
  • Granular scopes; not bound to one human user's employment
  • Placements: embed tabs and widgets in the portal UI
  • App-level event.bind subscriptions that survive personnel changes
  • Required path for anything distributable via Bitrix24.market

Our Recommendation Matrix

One-way lead feed from your website? Webhook, under a service account, with the URL in a secrets manager. Two-way ERP sync running for years? OAuth app — token rotation and user-independence justify the setup cost. Anything with UI inside Bitrix24? App, no choice. Quick internal script? Webhook, then delete it when done. When in doubt for production systems, we default to apps; for prototypes and internal tools, webhooks.

Security Checklist for Either Option

  • Create the webhook or install the app under a dedicated service user, not a person's account
  • Grant only the scopes the integration needs
  • Store secrets and tokens in a secrets manager or environment config, never in code or spreadsheets
  • Validate the application token on incoming event calls
  • Log every call and alert on repeated failures
  • Rotate webhook URLs when someone with access leaves

Want a Second Opinion on Your Own Setup?

Tell us what you run today and what you are deciding. A senior consultant replies within one business day with a straight recommendation.

Frequently Asked Questions

Are Bitrix24 webhooks secure enough for production?

Yes, if treated as credentials: service-account creation, minimal scopes, secret storage, no logging of URLs, and rotation policy. Most breaches we have seen were webhook URLs pasted into ticket systems — process failures, not platform ones.

Can I start with a webhook and migrate to an app later?

Yes, and it is a common path. If you structure your integration with the API client behind an interface, swapping webhook auth for OAuth tokens is a contained change.

Which is better for a Bitrix24 Marketplace app?

An OAuth app. Marketplace apps must be installable on many portals, which needs OAuth authentication; inbound webhooks are tied to a single portal and user.

Ready to make your CRM work like a real business operating system?

Let Tech Titan connect your leads, workflows, automations, communications, and reporting inside one intelligent CRM ecosystem.