OpenClaw Cloud — API & setup
Note: This documentation describes planned API capabilities. Features and endpoints are subject to change as the platform evolves. Contact us for current availability.
This page describes how to connect applications to OpenClaw Cloud — the managed control plane for OpenClaw workloads — including authentication, environments, and event delivery. It does not cover storefront or billing flows; those live in product-specific guides.
For integration support, please contact us.
Regions & base URL
Each deployment runs in a single region. Set OPENCLAW_CLOUD_REGION and point clients at your workspace base URL (shown in the OpenClaw Cloud console). Use separate staging and production workspaces so keys and webhooks never overlap.
Authentication
API and CLI calls use a workspace-scoped key. Send it in the Authorization: Bearer <OPENCLAW_CLOUD_API_KEY> header. Rotate keys from the console; old keys stop working after the overlap window you configure.
Webhooks & events
Register HTTPS endpoints to receive signed delivery notifications (connector sync, job lifecycle, policy updates). Verify the X-OpenClaw-Signature header with your workspace signing secret; failed deliveries retry with exponential backoff.