Complete REST & CGI API Reference
Full endpoint directory, request methods, query parameters, JSON payload schemas, and error codes.
6 min read · Updated
Complete REST & CGI API Reference
All QManager backend functions can be automated via standard HTTP JSON requests.
API Conventions & Headers#
- Base URL (OpenWRT):
http://<router_ip>/cgi-bin/quecmanager/ - Base URL (RM520N):
http://<modem_ip>/cgi-bin/quecmanager/ - Headers:
Content-Type: application/json- Cookie session header (if authentication is active)
Signal & Cellular Endpoints#
GET /get_signal.sh#
Returns live cellular signal metrics for all active carriers.
Response Schema:
JSON
{
"status": "success",
"data": {
"carrier": "T-Mobile",
"network_type": "5G-SA",
"band": "n41",
"bandwidth": 100,
"pci": 184,
"earfcn": 518970,
"rsrp": -82,
"rsrq": -11,
"sinr": 22.5,
"rssi": -65,
"mimo": {
"ant0": -82,
"ant1": -84,
"ant2": -83,
"ant3": -85
},
"ca": [
{ "band": "n41", "width": 100, "role": "PCC" },
{ "band": "n71", "width": 20, "role": "SCC1" }
]
}
}Configuration Endpoints#
POST /set_band.sh#
Locks or unlocks specific LTE/NR bands.
Request Payload:
JSON
{
"lte_bands": ["B2", "B66"],
"nr_bands": ["n41", "n77"]
}AT Command Endpoints#
POST /at_command.sh#
Executes an arbitrary AT command through the serialized broker.
Request Payload:
JSON
{
"command": "AT+QGMR"
}Response Schema:
JSON
{
"status": "success",
"command": "AT+QGMR",
"response": "RM520NGLAAR03A03M4G
OK"
}