Skip to content

Quick start ​

Your first successful API call, in about five minutes. This uses the api-key path, which needs no OAuth flow — you are calling your own account.

1. Create an integration ​

In the left menu of the Bito admin panel open Integration → Integration and press Custom integration. In the Create integration dialog press + Create next to External integration.

Fill in a name, leave the rest empty for now, and press Save. Field-by-field detail is in Create an integration.

2. Copy the three values ​

Saving shows client_id, secret and api_key. The secret is shown here once and never again — copy all three somewhere safe before closing the dialog, see Your credentials.

For this quick start you only need api_key. It looks like mycompany:9ad41c0e7b3f28d5610ac94e7f1b26d8.

3. Install it ​

An integration is created, not installed. Until it is installed, every API call made with its credentials fails with Integration is not installed.

On the Integration page, open your new integration from the Installed list and press Install. Installing also fires your redirect_uri and webhook_uri if you set them — see Install & uninstall hooks.

4. Make a call ​

List queries are POST — their filters travel in the body. Reads of a single record are GET, updates PUT, deletes DELETE.

bash
curl -X POST \
  'https://api.bito.uz/integration-api/integration/api/v2/product/get-paging' \
  -H 'api-key: mycompany:9ad41c0e7b3f28d5610ac94e7f1b26d8' \
  -H 'Content-Type: application/json' \
  -H 'Accept-Language: en' \
  -d '{ "page": 1, "limit": 5 }'

Response

json
{
    "code": 0,
    "message": "Success",
    "status_code": 200,
    "data": {
        "total": 1043,
        "data": [
            { "_id": "6712f0a9c4d1e87b3a0f9911", "name": "Espresso" }
        ]
    },
    "time": "2025-05-01T12:00:00Z"
}

code: 0 means success. The rows are at data.data, the count at data.total.

TIP

Got 401? The header is api-key, not Authorization, and the value includes the username part before the colon. Got 404? Check the base URL — it ends with /integration/api/v2/.

5. Pick your path from here ​

You are buildingRead next
Something for your own account onlyCalling the API, then the API reference — or a widget for your own account if it needs a screen inside Bito
A marketplace API integration many merchants installBecome a Bito developer, then read the OAuth 2.0 overview
A public widget that appears inside BitoYour app page, then Custom widgets
Something that reacts to data changesData webhooks

When it works, submit it for review. Public widgets have separate app-card and release reviews; approval makes the app installable, never automatically installed.

Bito 2.0 Integration API