Becoming a Bito developer

You do not need developer status to build an API integration or widget for your own Bito account. You need it when you want to create an app that other tenants can discover and install from the Bito marketplace.

Goal	What to use
Integrate only your own company	Integration → Integration → Custom integration
Run your own widget only in your account	Private widget
Publish an API integration or widget for other tenants	Request developer access, then use Integration → My apps

The public path follows the same broad model as an amoCRM technical account: a dedicated developer surface, versioned releases and a moderation queue. Unlike amoCRM's technical-account process, Bito grants developer status to the owner of your existing Bito account; you do not create a separate account for each app.

Request access

There is no self-service signup. Contact the platform owner through one of these channels:

Channel	Address
Email	kahero@unical.uz
Phone	+998 93 123 37 00
Telegram	t.me/kahero_unical

Include enough context to route the request: your Bito account, the product you plan to integrate, whether it includes a custom widget, and who will own support and the privacy policy. These details speed up review; they are not a second application form.

What changes after approval

An active developer gets Integration → My apps. From there the account owner can:

• create API-only apps and apps that ship widget code;
• claim a permanent app code;
• manage store cards in the selected languages;
• create semantic versions and upload widget.zip archives;
• test a private version in the developer's own tenant;
• submit or withdraw the app card and widget releases independently;
• view release history, installation statistics, reviews and integration keys.

Credentials belong to the app, not to a release. The client_id remains permanent; the secret and API key can be reissued from the Keys tab.

Developer states

developer_status	What you can do
absent	Use private integrations and private widgets in your own account. My apps shows the contact channels above.
active	Create and edit apps, test versions, submit cards and releases, and withdraw open reviews.
suspended	Read-only access to your apps and release history. Existing tenant installations keep working, but you cannot publish changes.

Only the account owner can perform developer mutations. An ordinary employee of the same tenant cannot publish code in the company's name.

Prepare before building a public app

• a stable HTTPS backend for install, uninstall and webhook callbacks;
• a support email or support page for every published language;
• a public privacy-policy URL;
• the narrowest Integration API permissions your app needs;
• a versioned, reproducible widget.zip build if the app runs inside Bito;
• a test case that a moderator can reproduce in your developer tenant.

Next: Your app page.