API reference

API reference.

431 endpoints in 24 products. Pages, SDKs, the CLI and the MCP server are generated from one definition, so they list the same endpoints.

01

Products

ProductEndpointsCLI
Account10orbit account
Organization10orbit org
Services15orbit services
DNS30orbit dns
Shield20orbit shield
Pages7orbit pages
Link8orbit link
Verify8orbit verify
RPKI13orbit rpki
RIPE11orbit ripe
Compute4orbit compute
Webhooks8orbit webhooks
Partners9orbit partners
Mail48orbit mail
Realtime9orbit realtime
Stream16orbit stream
VOD17orbit vod
Talk10orbit talk
Meet12orbit meet
Storage7orbit storage
V-Gate94orbit vgate
Voice12orbit voice
S-Gate49orbit sgate
Billing4orbit billing
02

Conventions

  • Base URL https://dash.yunzheng.space/api/v1, token in Authorization: Bearer orb_….
  • read endpoints accept a read-only token; write endpoints need a read + write token.
  • “Console only” endpoints (tokens, sessions, checkout) accept a signed-in browser session and never a token.
  • Body fields marked * are required. Path parameters are positional arguments of the CLI command.
  • The machine-readable definition: GET /api/v1/openapi.json.
Next

Related

Getting started

How an Orbit account is organised, what lives where in the console, and the shortest path from signing in to serving a name from our network.

DNS hosting

Add a zone, point your registrar at our name servers, manage records: weighted answers, health-checked records, ALIAS at the apex, zone-file import.

Connect a hostname

Delegate the whole domain, delegate one hostname, or add a CNAME and leave your DNS where it is. What each one costs you and when to pick it.

← All documentation