BEX Express

BEX Express

This connector uses the BexExpress REST API, the API of the Serbian courier BEX Express (Bexexpress, Šabac): shipment status history, address labels as PDF, the address directory (municipalities, places, streets) BEX needs for a shipment, and the list of parcel shops and depots. Creating and cancelling shipments is included but installed switched off.

Setup (contract customers only)

1. You need a contract with BEX Express. New customers write to [email protected].
2. Ask for API access by e-mail to [email protected] and name the contract it is for.
3. BEX replies with an API key (sent as the X-AUTH-TOKEN header) and your KlijentId. Paste the key into BEX_API_TOKEN. Keep the KlijentId at hand: it identifies your own company as sender in a shipment (NameType 3, Name1 = KlijentId).
4. Install and run bex_express_list_municipalities to check the key.

Two hosts: lookups, tracking and labels run on https://integrations.bexexpress.rs/api; creating, cancelling shipments and the parcel shop list run on https://api.bex.rs:62503/ship/api/Ship. The same key works on both. Port 62503 must be reachable from where AnythingMCP runs (it is from AnythingMCP Cloud); a firewall that only allows 443 blocks those three tools.

Tracking: bex_express_get_shipment_history takes the BEX shipment number (e.g. 206897445, as printed on the label and returned when the shipment is created) and returns every scan with status, date, place and time zone, plus eventPrediction, the next expected event. Status codes: 1 registered, 11 picked up from the sender, 21 delivered, 25 to be returned to the sender, 30 returned to the sender, -21 address check by the call centre, -51 at customs.

Labels: bex_express_get_label returns the address labels of a shipment as a Base64 PDF in parcelLabel (state false and err on failure). page_size 6 prints one A6 label per page, 4 prints four labels on A4, starting at page_position (0 to 3). parcel_no 0 prints every parcel of the shipment, otherwise only that parcel. The PDF is large; ask for it only when the user wants to print or save the label.

Address directory: a shipment address uses BEX ids. bex_express_list_municipalities lists municipalities (opštine), bex_express_list_settlements the places (mesta) of one municipality with postcode, bex_express_list_streets the streets of one place (with the old street name where it changed). Use the ids as Municipalities, Place and Street with AdressType 3, or send the place id and the street name with AdressType 2, or both names with AdressType 1. BEX would return every place or every street of Serbia for id 0 (almost 100,000 streets, about 7 MB), so the connector requires a real municipality or place id.

Parcel shops: bex_express_list_parcel_shops lists parcel shops and BEX depots (about 120) with code, address, opening hours and coordinates; BEX answers state: false with err: "ok" here even when the list is complete; the code goes into ParcelShop of a shipment task for delivery to or pickup at a parcel shop. region_id 0 lists all.

Creating and cancelling shipments (switched off): bex_express_create_shipments announces shipments for pickup by a courier and bex_express_cancel_shipment cancels an announced shipment. Both act on real courier orders, so they are installed switched off: an admin turns them on deliberately. Before each call, show the user the full shipment (sender, receiver, parcels, cash on delivery, insurance, pay type) or the shipment number to cancel and wait for a yes. Every field of the BEX shipment structure must be present: send 0 for unused numbers and an empty string for unused text. shipmentId 0 creates a new shipment; the answer lists the new shipment numbers per shipment, with reqstate and reqerr for the request as a whole.

Errors: a wrong or missing key answers 401. Many BEX methods answer HTTP 200 with state: false and a text in err: read those fields before treating a call as successful.