/ BaseLinker

Is your BaseLinker actually working for you?

Five checks a person would click through panels for: sources, catalogues, this week's orders, where they pile up, and what ships without tracking. Read-only, and your token is never stored.

BaseLinker -> My account -> API. The check only reads; it cannot change anything, and the token is not stored.

/ What this checks

What the health check reads from your BaseLinker account, and how to read each line.

The token travels from your browser to our server, which uses it for four calls to the BaseLinker API: getInventories, getOrderSources, getOrderStatusList and getOrders, the last one restricted to orders confirmed in the past seven days. From the answers it counts catalogues, lists the connected order sources by name, counts the defined statuses, groups the week's orders by status and counts those whose package number field is empty. All four methods only read. The code does not write the token to the database, and if you add an email address, what is saved with it is the outcome and the level of each line, not the token.

A green tick is a plain count: catalogues, sources, statuses, orders in the week. An amber triangle is something to look at. No catalogues or no order sources means that part of the account is not connected. No confirmed orders in seven days can be a quiet week or a stopped integration. A pile-up line lists up to five statuses that each hold 20 or more of the week's orders. The tracking line says how many of the week's orders carry no package number. A red cross appears only when the first call fails, meaning the token was rejected or BaseLinker could not be reached, and the check stops there.

The check makes a single getOrders call and does not page through results, so in a busy shop the weekly figures cover only the first batch BaseLinker returns. The tracking count includes every order without a package number, also those not yet packed, cancelled or collected in person, so read it against your own process. A status holding many orders may be a final status where that is normal. Stock levels, product data, prices, marketplace listings and courier settings are not examined. If one line says a check could not be made, the remaining lines still stand. Compare the lines with what your team sees in the panel.

Where do I find my BaseLinker API token?
In the BaseLinker panel, open My account and go to the API section, where a token can be generated. The token is a long string that identifies your account to the API, and each request carries it in the X-BLToken header. Anyone who holds it can call the API as your account, so treat it like a password: do not send it by email or paste it into shared documents.
What is the BaseLinker API used for?
The BaseLinker API lets external programs work with an account without a person clicking through the panel. Typical uses are reading and adding orders, changing order statuses, managing products and stock in catalogues, and creating shipments. Requests are sent by POST to one connector address, with the method name and a set of parameters in JSON, and are authorised by the account's token.
Why do orders get stuck in one status in BaseLinker?
Orders move between statuses either by hand or through automatic actions. They collect wherever nothing moves them on: a status that waits for payment, for stock, for a shipping label or for someone to click. When one status holds a growing share of the week's orders, it is usually a step with no automatic action behind it, or one whose condition is not being met. Looking at what the stuck orders have in common is the quickest diagnosis.
Next

When one check is not the whole job.

Want these checks weekly, with a person fixing what they find?