Skip to content

Command 101 — View the detail lines of an orderdirect

Same call, new address. The two body parameters become path segments.

V2 checks an app permission on every call — V1 checked none — and a call whose permission is missing answers 400 with errorCode 15, the same status as an invalid payload (see 4.4). Grant these to the API user before porting the command; the names are the ones of the permission tree in flowww.

CallPermission
GET /order/{orderGID}/num/{orderGPartNum}/detail/{orderID}Stock Control - Orders → See product
GET /order/25/num/1Stock Control - Orders → See
API V1
curl --location --request GET 'https://euapi.flowww.net/v1/fwa_external_get.asp?cmd=101&doctor=USER_LOGIN&pass=USER_PASS&country=ES&key=SYSTEM_KEY&ClinicID=1' \
--data-urlencode 'OrderGID=25' \
--data-urlencode 'OrderGPartNum=1'
API V2
curl --location 'https://api.flowww.net/v2/order/25/num/1?clinicID=1' \
--header 'Authorization: Bearer <api_key>'
API V1API V2Notes
OrderGID{orderGID} in the path—
OrderGPartNum (optional, default 0){orderGPartNum} in the pathNow required. Send 0 when the order has not been split.
<Orders><Order>… one node per lineone order object with a Details[] arrayThe header fields and the lines come in the same payload.
OrderID, OrderProductID, OrderUnits, OrderPricesame names inside Details[]Plus OrderProductDesc, OrderComments, OrderTotal, OrderProviderName and the lot/traceability fields.

A single line can also be read on its own with GET /order/{orderGID}/num/{orderGPartNum}/detail/{orderID}.

  • V1 only showed the orders of the ClinicID sent. V2 shows any order of the system by its id: keep track on your side of which orders belong to which clinic (from GET /order?clinicID=).
  • An order or part that does not exist answers 404.