API reference

The Biklo Partner API lets a company sell on Biklo from the system it already runs — an ERP, a channel manager, a warehouse tool — without anyone opening the seller dashboard. It is a REST API over HTTPS: JSON in, JSON out, authenticated with a single bearer key.

It covers the whole lifecycle of a sale. You publish and price your catalogue, take the orders that follow, declare how each one is packed, buy the waybill and print the label, answer the buyer, and withdraw what you earned — plus the company settings and reference data you need to map your own records onto ours.

What it is not#

This is a seller API. It acts for exactly one company — the one your key belongs to — and every endpoint is scoped to what that company owns. There is no buyer-side surface: you cannot browse the marketplace, place an order, or read anyone else's listings. It is also not a copy of the dashboard; a few things that need a human decision, such as identity verification, stay there deliberately.

Two things that shape every call#

Money is always an integer in minor units, with its currency beside it. 12550 and RON, never 125.50. A seller trading cross-border holds several currencies at once, so there is no single balance and no bare amount anywhere in this API.

Everything is scoped to your key. A key carries a fixed set of scopes and belongs to one environment. A sandbox key is bk_test_, a live key is bk_live_, and presenting one to the other environment fails rather than doing something surprising.

Conventions#

Every response is wrapped in data, every failure uses the same error envelope with a machine-readable code, and every response carries a request_id worth logging — it is what support will ask you for. Lists are paginated and can be polled incrementally with updated_since, though a webhook is almost always the better answer.

Endpoints#

96 endpoints, in the order an integration is normally built. Base URL https://api.biklo.com · sandbox https://sandbox-api.biklo.com · OpenAPI · Postman