Command 101 — View the detail lines of an orderdirect
Same call, new address. The two body parameters become path segments.
Permissions
Section titled “Permissions”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.
| Call | Permission |
|---|---|
GET /order/{orderGID}/num/{orderGPartNum}/detail/{orderID} | Stock Control - Orders → See product |
GET /order/25/num/1 | Stock Control - Orders → See |
Before and after
Section titled “Before and after”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'curl --location 'https://api.flowww.net/v2/order/25/num/1?clinicID=1' \ --header 'Authorization: Bearer <api_key>'Field mapping
Section titled “Field mapping”| API V1 | API V2 | Notes |
|---|---|---|
OrderGID | {orderGID} in the path | — |
OrderGPartNum (optional, default 0) | {orderGPartNum} in the path | Now required. Send 0 when the order has not been split. |
<Orders><Order>… one node per line | one order object with a Details[] array | The header fields and the lines come in the same payload. |
OrderID, OrderProductID, OrderUnits, OrderPrice | same 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}.
What changes compared with V1
Section titled “What changes compared with V1”- V1 only showed the orders of the
ClinicIDsent. V2 shows any order of the system by its id: keep track on your side of which orders belong to which clinic (fromGET /order?clinicID=). - An order or part that does not exist answers
404.