Autoxing REST API Book
  • English
  • zh-CN
GitHub
  • English
  • zh-CN
GitHub
  • Guide

    • Getting Started
    • Start Moving
    • Getting Started with WebSockets
    • Robot Admin (Standalone Version)
  • Reference

    • REST API Principles
    • Map API
    • Move API
    • Current Map and Pose API
    • Overlays
    • Mapping API
    • IoT Devices
    • Device Information API
    • Robot Parameters API
    • System Settings
    • App Store API
    • Hostname API
    • Landmarks
    • Submaps
  • Services

    • Service API
    • Motion & Chassis Control
    • Localization
    • Mapping
    • Cargo Handling
    • Perception & Sensors
    • Calibration
    • Network
    • System & Maintenance
  • WebSocket

    • WebSocket Reference
    • Localization
    • Mapping
    • Navigation & Planning
    • Chassis & Safety
    • Cargo & Equipment
    • Perception & Cameras
    • Environment & Connectivity
    • System & Power
  • Other

    • Deprecations
    • Changelog

WebSocket Reference

Topics are used to receive real-time information from the robot. Use the following commands to start or stop listening to specific topics.

{"enable_topic": "TOPIC_NAME"}
{"disable_topic": "TOPIC_NAME"}

Since version 2.7.0, multiple topic names are supported. This requires the supportsEnableTopicList capability flag.

{"enable_topic": ["/actions", "/alerts", "/tracked_pose"]} // since 2.7.0
{"disable_topic": ["/actions", "/alerts", "/tracked_pose"]} // since 2.7.0

Protobuf Messages

Some topics are sent as binary protobuf WebSocket frames; others use JSON text messages. A connection can receive both formats. On servers that support it, append ?pb=1 to prefer protobuf for topics available in both formats.

Binary frames have this layout:

[topic_length: 1 byte][topic: UTF-8 bytes][flags: 1 byte][publisher_index: 1 byte, optional][payload]

The topic length is the number of bytes in the topic name. Flag bit 0 indicates a gzip-compressed payload; bit 1 indicates that the publisher index byte is present. Other flag bits are reserved. Decompress the payload when necessary, then decode it as ax_proto_msgs.RosMessageWrapper. Its type identifies the message, and the corresponding payload field contains the topic data.

The RosMessageWrapper definition lists the supported message types and payloads. The protobuf source directory contains their message definitions. These definitions are also available through the @kingsimba/axbot-sdk TypeScript SDK.

Topic index

Topics are grouped by function:

  • Localization — SLAM state, pose, global positioning, barcodes, and landmarks.
  • Mapping — map and costmap images, incremental updates, trajectory, and map-quality diagnostics.
  • Navigation & Planning — planning state, paths, follow-target control, robot model, and signals.
  • Chassis & Safety — wheels, odometry, IMU, bumper, and push handle.
  • Cargo & Equipment — jack, roller, rack, pallet, and trailer state.
  • Perception & Cameras — point clouds, detected objects, and camera streams.
  • Environment & Connectivity — nearby robots, auto doors, V2X beacons, and GNSS/INS.
  • System & Power — battery, sensor power, alerts, app events, and I/O pins.

Localization

TopicDescription
/slam/stateSLAM state, position reliability, and positioning quality.
/tracked_poseRobot pose in the world frame.
/global_positioning_stateProgress and result of start_global_positioning.
/collected_barcodeBarcodes seen by the robot, with their map poses.
/landmarksLandmarks collected for the current map.

Mapping

TopicDescription
/mapCurrent map image; updated once in localization mode, repeatedly while mapping.
/map_v2Large map images served through cacheable data_url links.
/maps/5cm/1hzLow-resolution costmap used for path planning.
/maps/1cm/1hzHigh-resolution costmap used for collision detection.
/incremental_mapNew obstacles and cleared space detected since the map was built.
/updated_map_sliceA grayscale slice of a freshly updated map region.
/trajectoryThe robot's trail, complete in mapping mode and trimmed in localization mode.
/env_match_mapHow well the live point cloud matches the stored map.
/env_symmetry_mapHow ambiguous the environment is for localization.

Navigation & Planning

TopicDescription
/planning_stateExecution state of the current move action.
/pathThe planned global path.
/local_pathThe local planner's path (debug).
/follow_target_stateSend follow-target control messages to the robot.
/robot_modelDynamic footprint, including an attached rack.
/platform_monitor/travelled_distanceDistance and duration of the current move.
/robot_signalTurn-signal and brake-light state.

Chassis & Safety

TopicDescription
/wheel_stateControl mode, emergency stop, and wheel release state.
/odom_stateLidar odometry reliability and covariance (debug).
/fused_sensor_stateSlipping, pushing, and stillness estimates.
/imu_stateRaw IMU data and gyro bias calibration state.
/bumper_stateFront and rear bumper switch state.
/push_handle_statePush-handle mode and activation.

Cargo & Equipment

TopicDescription
/jack_stateJack position, progress, and self-check state.
/roller_stateRoller state: hold, loading, or unloading.
/detected_rackRack detected in front of the robot, with dimensions.
/detected_rack_statesReal-time rack occupancy observations.
/map_rack_statesAccumulated occupancy of all racks on the map.
/detected_palletsPallets detected around the robot, with dimensions.
/detected_trailerTrailer detected behind the robot, with hitch geometry.

Perception & Cameras

TopicDescription
/scan_matched_points2Combined LiDAR point cloud used for SLAM.
/horizontal_laser_2d/matchedPer-device point cloud for debugging.
/vision_detected_objectsObjects detected by the vision system (experimental).
/rgb_cameras/front/videoH.264 video from the RGB cameras.
/rgb_cameras/front/compressedJPEG stills from the RGB cameras.
/depth_camera/downward/imageDepth-camera images as base64 PNG.
/external_rgb_camera_controlControl and data channels for external RGB cameras.

Environment & Connectivity

TopicDescription
/nearby_robotsOther robots sensed around the robot.
/nearby_robot_footprintsFootprints that go with /nearby_robots digests.
/nearby_auto_doorsState and polygons of nearby automatic doors.
/v2x_health_stateReception health of V2X beacons.
/devpvtRaw GNSS/INS navigation data from the CHC sensor.

System & Power

TopicDescription
/battery_stateBattery voltage, current, and charge level.
/detailed_battery_stateBattery state plus cell voltages, capacity, and health.
/sensor_manager_stateWhether the sensors are awake, awakening, or sleeping.
/alertsCurrently active alerts.
/app_eventsApplication event stream (protobuf).
/get_device_info_briefRequest device and firmware info over the WebSocket.
/io_pins_stateLogical IO pin state and output-pin control.
/raw_io_board_stateRaw IO board input/output pin state.
Edit this page
Last Updated: 10/30/26, 7:15 PM
Contributors: FengZhaolin
Next
Localization