How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Bear Robotics Mission API

Basic mission-related operations

Bear Robotics Mission API is one of 9 APIs that Bear Robotics publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Mission. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and a changelog.

This API exposes 9 operations across 9 paths, and defines 42 schemas. It is described by OpenAPI 3.2.0, at version 1.3.0.

Requests are made against a single base URL, https://api.bearrobotics.ai.

9 operations 9 paths 42 schemas 9 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.3.0
Base URL
https://api.bearrobotics.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Bear Robotics Mission API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — JWT token obtained from the /authorizeApiAccess endpoint

Paths & Operations 9

Across 9 paths, the API surfaces 9 operations — 9 POST. Each is listed below with its method, path, parameters, and response codes.

Mission 9

Basic mission-related operations

POST
/v1/mission/append
API service append mission
APIService_AppendMission body → 200400401500503504
POST
/v1/mission/append-batch
API service append mission batch
APIService_AppendMissionBatch body → 200400401500503504
POST
/v1/mission/create
API service create mission
APIService_CreateMission body → 200400401500503504
POST
/v1/mission/create-batch
API service create mission batch
APIService_CreateMissionBatch body → 200400401500503504
POST
/v1/mission/update
API service update mission
APIService_UpdateMission body → 200400401500503504
POST
/v1/mission-workflow/create
API service create mission workflow
APIService_CreateMissionWorkflow body → 200400401500503504
POST
/v1/goal/skip
API service skip goal
APIService_SkipGoal body → 200400401500503504
POST
/v1/mission-status/clear
API service clear mission status
APIService_ClearMissionStatus body → 200400401500503504
POST
/v1/robot/charge
API service charge robot
APIService_ChargeRobot body → 200400401500503504

Schemas 42

The contract defines 42 schemas that model the data the API accepts and returns. The most detailed are Pose (3 properties), AppendMissionRequest (2 properties), BussingPatrolMission (2 properties), UpdateMissionRequest (2 properties). Each schema is shown below with its type and property counts.

DeliveryPatrolParams
object
Parameters for a delivery patrol mission (reserved for future use)
NavigateMission
object
A simple mission with a predefined goal
1 property
TraverseMission
object
A traverse mission that navigates to one or more goals
2 properties
TrayMapping
object
Maps a tray to a delivery goal.
2 properties
DeliveryMission
object
A delivery mission that navigates to one or more goals, stopping at each for a time limit or until weight is removed
2 properties
MissionWorkflow
object
Preset workflow to run. Only one workflow type may be set at a time.
CreateMissionBatchRequest
object
Request object for atomically creating multiple missions
2 properties 2 required
AppendMissionResponse
object
1 property
TraversePatrolMission
object
A traverse patrol mission that navigates to one or more goals and continuously loops through the goals stopping at each for a time limit
2 properties
AppendMissionRequest
object
Request object for appending a mission
2 properties 2 required
CreateMissionWorkflowRequest
object
Request object for creating a mission workflow
2 properties 2 required
CartiMission
object
Carti missions are specific to the Carti robot family
TraverseParams
object
Parameters for a traverse mission (reserved for future use)
SkipGoalResponse
object
1 property
Goal
object
Goal represents a target destination or pose for the robot to navigate to.
CreateMissionRequest
object
Request object for creating a new mission
2 properties 2 required
ClearMissionStatusRequest
object
Request object for clearing the robot's mission status
1 property 1 required
SkipGoalRequest
object
Request object for skipping a goal
1 property 1 required
UpdateMissionResponse
object
ServiWorkflow
object
Servi preset workflows. Each type takes only goals (or a single goal for birthday) with no params.
ChargeRobotResponse
object
1 property
NavigateAutoMission
object
A mission that automatically selects the best available goal from the provided list
1 property
Mission
object
Represents a mission that can be assigned to a robot. Only one mission type can be set per Mission instance.
BussingMission
object
A bussing mission that navigates to one or more goals, stopping at each for a time limit or until weight is added
2 properties
UpdateMissionRequest
object
Request object for updating a mission
2 properties 2 required
ClearMissionStatusResponse
object
1 property
BussingParams
object
Parameters for a bussing mission (reserved for future use)
BussingPatrolParams
object
Parameters for a bussing patrol mission (reserved for future use)
BaseMission
object
Base missions are applicable to all robot families
CreateMissionWorkflowResponse
object
1 property
ChargeRobotRequest
object
Request object for sending a robot to charge
1 property 1 required
CartiWorkflow
object
Carti preset workflows. Each type takes only goals with no params.
CreateMissionBatchResponse
object
1 property
DeliveryParams
object
Parameters for a delivery mission
1 property
TraversePatrolParams
object
Parameters for a traverse patrol mission (reserved for future use)
BussingPatrolMission
object
A bussing patrol mission that continuously loops through goals, stopping at each for a time limit until weight exceeds a threshold
2 properties
DeliveryPatrolMission
object
A delivery patrol mission that continuously loops through goals, stopping at each for a time limit until all weight is removed
2 properties
CreateMissionResponse
object
1 property
Pose
object
Represents the robot's pose on the map.
3 properties
AppendMissionBatchResponse
object
1 property
ServiMission
object
Servi missions are specific to the Servi robot family
AppendMissionBatchRequest
object
Request object for atomically appending multiple missions
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bear-robotics-mission-api-openapi.yml Raw ↑

Other APIs Bear Robotics publishes across the network.

Bear Base API
Bear Robotics Carti API
Bear Robotics Fleet Management API
Bear Robotics Localization & Navigation API
Bear Robotics Locations & Maps API
Bear Robotics Robot Status API
Bear Robotics Robot System API
Bear Robotics Servi API
Where this information came from

This is an independent, third-party profile of Bear Robotics Mission API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.