Sell on Biklo from the system you already run

A public, key-authenticated API so your ERP, channel manager or warehouse system can list products, fulfil orders, answer buyers and move money — without anyone opening the Biklo seller dashboard.

What Biklo is#

Biklo is a marketplace for bikes and everything around them — mountain and road bikes, e-bikes, frames, components, wheels, apparel and accessories — where private sellers and companies list side by side. Buyers pay on the platform rather than on delivery, and we hold that money until the order is complete, which is what makes buying a used frame from a stranger a reasonable thing to do.

We run the parts a seller would otherwise have to run themselves:

• Payments and buyer protection. The buyer pays Biklo. The money is held until the parcel arrives and the return window passes, and only then does it become yours to withdraw.
• Delivery. We quote the courier, buy the waybill and track the parcel. You pack the box and hand it over.
• Returns and disputes. A buyer's return runs through us, on the same rules for everyone selling here.
• Invoicing of our own fees. We issue you an invoice for what you owe us; you invoice the buyer for what they bought.

So a sale on Biklo involves more moving parts than a listing site: an order has a lifecycle, money sits in a wallet before it is yours, and a fee may be charged to the buyer or absorbed by you depending on how your company is configured. This API exposes all of it.

Who this is for#

Companies selling on Biklo, and the software vendors who integrate for them. If you keep your stock, prices and orders in a system of record — an ERP, a channel manager, a warehouse tool, your own shop backend — this is how that system talks to Biklo instead of someone retyping it.

It is a seller-side API. It acts for exactly one company, the one your key belongs to, and only ever on what that company owns. There is no buyer-side surface here.

Three steps to a working integration#

• 1Sign in to Biklo

  With the company account that owns the listings. A private seller account cannot use this API.

• 2Create an integration

  Dashboard → API integrations → API access. You get a test key and a live key, both shown once.

• 3Make your first call

  Against the sandbox, where nothing is real — no live listings, no money, no courier.

How to start walks through all three with the screens you will be looking at, then adds the two that matter afterwards: pointing a webhook at your system, and narrowing the key's permissions before you go live.

Start here#

Quickstart — a key, your first call, your first product. Fifteen minutes.

Environments and the sandbox — a blank environment with real reference data, where nothing you do is real. No live listings, no real orders, no money moves, and no courier is ever contacted.

Authentication — bk_test_ and bk_live_, scopes, and what happens when a key is presented to the wrong environment.

What you can do#

Three things worth knowing before you start#

Money is always minor units plus a currency. 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 number anywhere in this API.

Webhooks beat polling. Register an endpoint and we tell you when an order arrives, a buyer writes, or a payout moves. Ten ERPs polling /orders on a timer helps nobody.

The sandbox is not a copy of production. It holds reference data — categories, fields, geo, couriers — and no personal data at all. Your own company and catalogue are copied in when you create your first key, so there is something real to map against.

Keeping up#

The changelog publishes RSS and Atom. Subscribe your reader or your CI: it is how you learn an endpoint moved before one of your customers tells you.