Overview

A Bito integration is an external application that uses the Integration API and may also ship a custom widget that runs inside the Bito admin panel.

Start by choosing the right distribution path:

Path	Who can install it	Developer account	Moderation
Private integration or private widget	Your own Bito account	Not required	No marketplace review; the archive is still validated and the account owner must consent
Public API integration	Any Bito tenant from the marketplace	Required	Marketplace card review
Public integration with a custom widget	Any Bito tenant from the marketplace	Required	Marketplace card review and widget-release review

This is the same useful separation made in the amoCRM integration overview: build privately first, then use a developer-only workflow for a public marketplace app. The field names, package format and moderation states below are Bito's own contracts.

Public-widget journey

  Developer account
        |
        |  Create app -> copy credentials -> claim permanent app code
        v
  Marketplace card (name, listing, URLs, permissions, support/privacy)
        |
        |  Create version -> upload widget.zip -> validate -> test locally
        v
  Release review: draft -> queued -> testing -> approved
        |
        |  Submit the marketplace card for its separate review
        v
  Card review: draft/changed -> pending -> approved
        |
        v
  PUBLIC: tenants can find, install and consent to the approved release

The two reviews are intentionally independent:

• the app card is the store-facing identity, listing, URLs, permissions and commercial information;
• a release is one exact version of widget.zip, its release notes and a snapshot of the listing.

Approving a release makes that code runnable. It does not publish the app by itself. Approving the card makes the app public, but a widget app cannot be published with a locally activated or otherwise unmoderated current release.

Credentials do not change on publication

Your client_id, secret and api_key are issued when the integration is created. Publication changes visibility and approved code; it does not mint a second production identity.

WARNING

The secret is shown once, at creation, and cannot be read back. If the secret or the API key is lost or compromised, reissue both with Reissue keys on the Keys tab and update every caller immediately — see Rotating credentials.

Start here

• Quick start for an API call against your own account
• Becoming a Bito developer for a public marketplace app
• Your app page for the complete public-widget workflow
• Custom widgets overview and the widget.zip format for the runtime contract