Prefer env vars at build time (GOOGLE_SITE_VERIFICATION, BING_SITE_VERIFICATION, YANDEX_VERIFICATION, BAIDU_SITE_VERIFICATION, NAVER_SITE_VERIFICATION). Optionally paste meta tags below this comment for a one-off deploy. DNS TXT alternatives: see docs/indexing-playbook.md --> Boston Dynamics Orbit | Robomap Docs
Robomap Docs
Open app

Robomap Docs

Boston Dynamics Orbit

Connect Boston Dynamics Orbit to sync Spot robots into Robomap and import missions.

What it does

Connect a Boston Dynamics Orbit instance for Spot robots: list robots as Robomap devices, show status and mission context, and import mission runs / anomalies into Robomap data views.

Official Orbit API concepts: Orbit API.

Get an Orbit API token

  1. Sign in to your Orbit web UI.
  2. Open Settings → Developer Features → API.
  3. Create an API token.
  4. Note your Orbit site URL (for example https://orbit.example.com).

Connect in Robomap

  1. Go to Account → Integrations → Boston Dynamics.
  2. Enter the Orbit site URL and API token → Connect. The token is stored encrypted.
  3. Click Sync robots to pull Spot robots and optionally create Robomap devices.
  4. Click Import missions to pull recent runs and anomaly counts into local import records (visible on the integration page and usable by data views).

Troubleshooting

  • Connect fails — confirm the Orbit URL is reachable from Robomap and the API token is active.
  • TLS / certificate errors — production Orbit should use a valid certificate. Lab instances with self-signed certs require administrator configuration; do not disable TLS verification on production.
  • Robots missing after sync — run Sync robots again; verify robots appear in Orbit’s own inventory first.