SCALEWEBLINK · v1.5 · REST / JSON

ScaleWebLink – user manual and REST API

ScaleWebLink v1.5 HTML manual: protocol setup, POST JSON, MID and PIN, weight data, ERR01–ERR10, API test and simulator.

Slovenska navodila ↗

1. Purpose and operation

ScaleWebLink communicates with a scale through SSL-encrypted REST web services. The scale connects to the cloud through CloudScaleLink. An external system sends an action and receives a JSON response.

Each CloudScaleLink module has a unique MID (Module ID) and PIN (Module PIN). Together, they authorize access to the scale. For virtual CloudScaleLink, MID and PIN are provided by email.

You need a Scale Monitor account, a connected scale with a suitable protocol or a simulator, and service access. Supported commands and available fields depend on the scale and protocol.

2. Quick start

Register using your partner link or register.scale-monitor.com and sign in to Scale Monitor.
Add your scale and check its CloudScaleLink connection.
Open Menu → Protocol → ScaleWebLink.
Select Protocol and Protocol version.
Assign a suitable weight-reading command to Get_Weight.
Open API test, select the action and send it.
Check the response, then integrate the POST request into your application.

3. Protocol, actions and commands

In Menu → Protocol → ScaleWebLink, select the protocol and version for the connected scale. The original manual uses Mettler Toledo MT SICS as an example.

The settings table has two columns: Action is the action name your application calls; Command is the command sent to the scale.

The preset action name Get_Weight cannot be changed, but its assigned command can be selected. Click Add to create a row, enter your custom action name and select the command.

Field / code	Meaning and usage
`Get_Weight → SIX1`	Example weight request using MT SICS, version MT SICS_1.
`Tare → T`	MT SICS taring example: the Tare action sends command T.

MT SICS examples are not universal commands for other scales. Check available functions in the connected device protocol.

4. POST request and authorization

Post a JSON object with three fields. Field names are lowercase.

Field / code	Meaning and usage
`mid`	CloudScaleLink module ID.
`pin`	CloudScaleLink module PIN.
`action`	Get_Weight or the name of a saved custom action.

For a physical module, MID and PIN are on its label. For a virtual module, use the credentials provided by email.

API address: use the service URL assigned to your connection. PDF v1.5 does not specify a concrete endpoint URL; contact support if you do not have it. The example below uses an explicitly marked placeholder, not a working endpoint.

{
  "mid": "yourMID",
  "pin": "yourCSLPIN",
  "action": "Get_Weight"
}

cURL

# Replace the placeholder URL and module credentials.
curl --request POST 'https://YOUR-SCALEWEBLINK-ENDPOINT' --header 'Content-Type: application/json' --data '{"mid":"yourMID","pin":"yourCSLPIN","action":"Get_Weight"}'

5. JSON response

ScaleWebLink returns a JSON object. The example retains the response from manual v1.5; data availability and content follow the scale protocol.

Field / code	Meaning and usage
`error`	0 = no error; 1 = an error occurred.
`errorCode`	Error code; see chapter 7.
`errorMsg`	Short error description.
`scaleResponse`	Raw string received from the scale in response to the command.
`dateTime`	UTC date and time when the action was executed.
`weightData`	Object containing available weight data.

Manual v1.5 shows dateTime as a textual UTC date. The original website also shows a numeric timestamp and weights as strings. Check the actual response of your service and selected protocol, and convert types accordingly; do not assume a single format.

{
  "error": 0,
  "errorCode": null,
  "errorMsg": "",
  "scaleResponse": "SIX1 S 0 N R R 0 0 0 1 P 0.068     0.000   0.068 kg",
  "dateTime": "Wed, 04 Sep 2024 11:07:51 GMT",
  "weightData": {
    "net": 0,
    "gross": 0.068,
    "tare": 0.068,
    "unit": "kg",
    "stability": 1,
    "expectedResponseStatus": null,
    "expectedResponseMsg": null
  }
}

6. weightData fields

Field / code	Meaning and usage
`net`	Net weight; null if not received.
`gross`	Gross weight; null if not received.
`tare`	Tare value; null if not received.
`unit`	Weight unit; null if not received.
`stability`	null = no data; 0 = unstable scale; 1 = stable scale.
`expectedResponseStatus`	null = not configured; 0 = response not OK; 1 = response OK.
`expectedResponseMsg`	Message configured for the corresponding command in protocol settings.

null is not zero weight. Before using a measurement, check errors, required fields, unit and stability. Example values are not reference measurements; validate parsing with the actual scale.

7. Error codes and troubleshooting

If an action fails, the response contains an error code. Check JSON and action configuration first, then connectivity and the scale response.

Field / code	Meaning and usage
`ERR01`	Required POST data is missing or JSON is invalid. Check the request body and JSON syntax.
`ERR02`	Module ID (MID) is missing. Include mid.
`ERR03`	Module PIN is missing. Include pin.
`ERR04`	Action is missing. Include action.
`ERR05`	The action was not found among saved actions. Check its name and configuration.
`ERR06`	No Scale Monitor was found connected to the received topic. Check the topic and connection.
`ERR07`	Command data was not found. Select a valid command for the action.
`ERR08`	The command string is missing. Check the command property in the selected protocol.
`ERR09`	Service is busy: another client is communicating with the scale using the same MID and PIN. Serialize requests and retry later.
`ERR10`	Timeout: no response was received within the allotted time. Check scale connectivity and protocol.

8. API test

Open Protocol → ScaleWebLink.
Click API test at the bottom of the page.
Select a saved action in the new window.
Send the action and inspect the response display.

Manual example: Protocol: MT SICS, Version: MT SICS_1, Action: Get_Weight, assigned command SIX1. If testing fails, use the error table and check the selected command.

9. Simulator without a physical scale

Open Scale simulation from the top-left menu.
Click the plus icon in the Presets tab.
Enter the desired simulator data.
Set Connection type to Scale link and click Save.
The generated MID and PIN appear at the top after saving.
Click the saved simulator in Presets to connect it to the cloud.
Use the simulator MID and PIN in ScaleWebLink requests.

The simulator supports API development and testing. Before using the integration in your process, check the actual scale, protocol and required actions.

10. Integration recommendations and support

Keep MID and PIN on the server side; do not expose them in public web code or logs.
Serialize requests to the same scale. ERR09 indicates that communication is busy.
For ERR10, check connectivity and scale response. Do not blindly retry state-changing actions: without a response, you cannot know whether the action was executed.
Treat unavailable fields as missing data, not 0.
Before storing a result or continuing a process, check success, unit and required stability.

For additional information and technical support: support@scale-monitor.com.

This documentation is based on ScaleWebLink v1.5. Examples explain the interface and must be adapted to your configuration.

Frequently asked questions about ScaleWebLink

What is ScaleWebLink?

ScaleWebLink is a web service that communicates with a scale through CloudScaleLink using REST requests and JSON responses.

Can I use an existing scale?

Yes, if it can connect through CloudScaleLink and its communication protocol can be configured. We check the manufacturer, model, connector and required commands before integration.

Can I tare a scale from my application?

Yes, if the scale and protocol support taring. Define an action and its command in Scale Monitor, then call the action through ScaleWebLink.

Is an internet connection required?

Yes. The documented connection uses a cloud service and a connected scale or simulator.

Can I test without a physical scale?

Yes. The Scale Monitor simulator generates a MID and PIN for testing. API test checks actions and displays responses.

Are all weight fields always available?

No. net, gross, tare, unit and stability depend on the scale response and protocol. null means that data was not received.

ScaleWebLink · v1.5 · PRECIZ / Scale Monitor

Enquire ↗