Skip to content

v1.3

Release: Bear Cloud API v1.3

June 2026

Release
servi-26.02
carti-26.02
amr-26.02

Note

Bear Cloud API v1.3 is designed to be backward compatible with v1.2, so there should not be any issues working with the v1.2 gRPC APIs.

New in v1.3: a Postman collection for the REST API

v1.3 ships a ready-to-import Postman collection covering every unary REST endpoint, with API-key (JWT) authentication wired up — import it for quick, code-free testing. See Developer Resources for details.

Minimum Robot Software Versions (for full support)

  1. Servi: 26.02
  2. Carti: 26.02

Key features

  • Webhooks — register HTTP callbacks to receive robot events without holding a streaming connection
  • New navigation monitoring with the SubscribeNavigationStatus RPC and a navigation_state field on robot status
  • Fleet-wide online monitoring with the SubscribeOnlineStatus RPC
  • Atomic mission batches for creating and appending multiple missions in a single request
  • Stronger map integrity verification with an MD5 checksum on map image files

New RPCs

Webhooks

  • CreateWebhook - Create a webhook subscription that delivers an HTTP request to a configured URL each time a matching event occurs on any of the selected robots. Supports custom request templates, headers, and field filters
  • ListWebhooks - List all webhook subscriptions for a distributor
  • DeleteWebhook - Delete an existing webhook subscription by ID (soft delete)

Robot Status

  • SubscribeNavigationStatus - Stream navigation-related state for a fleet of robots, selected by robot IDs or location, including whether each robot is currently stuck (unable to make navigation progress) and the reason when known. Each response carries the robot_id it pertains to. Prefer this over SubscribeRobotStatus when only the navigation signal is of interest
  • SubscribeOnlineStatus - Stream the cloud-to-robot connection state for a fleet of robots, selected by robot IDs or location

Mission

  • CreateMissionBatch - Atomically create multiple missions in a single request. If any mission fails validation or creation, no missions are created
  • AppendMissionBatch - Atomically append multiple missions to the end of the mission queue. If any mission fails validation or append, no missions are appended
  • ClearMissionStatus - Clear the robot's mission status. Fails if the robot is on a running or paused mission

Enhanced RPCs

Robot Status

Localization & Navigation

  • SubscribeEmergencyStopStatus now supports fleet-level subscriptions through core.RobotSelector, allowing selection by a list of robot IDs or by location. The previous single-robot robot_id field is deprecated but remains supported for backwards compatibility

Maps & Locations

  • GetMap and GetCurrentMap now return an md5_checksum (32-character lowercase hex string) in MapImageFileInfo for integrity verification. The existing CRC32C checksum field is deprecated in favor of md5_checksum

Developer Resources

  • Postman collection — a Postman collection is now available for the v1.3 REST API, covering all unary (non-streaming) endpoints and API-key (JWT) authentication. Import it for quick, code-free testing, or browse the published documentation

New API Customers

Please contact your Account Manager to discuss API use cases and request API keys.

How to Upgrade

  1. Review the v1.3 API endpoint specification.
  2. Upgrade robot software to the compatible versions listed above.
  3. Download and compile the updated v1 Protobuf library. See our Programming Guide and examples for relevant endpoints.
  4. Test your integration against the new version.