Back to documentation

OpenClaw Cloud — API & setup

HappyClaw integrates with OpenClaw Cloud for managed runtime, connector orchestration, and signed event delivery. This page is about cloud configuration and APIs — not payment flows, checkout URLs, or processor webhooks. Questions? Contact us.

Workspace & region

In the OpenClaw Cloud console, create a workspace and select a region. Your assigned API base URL and regional settings apply to all connectors and automation running under that workspace.

Environment variables

Typical server-side configuration (names may vary by deployment):

  • OPENCLAW_CLOUD_API_KEY — workspace API key (server only)
  • OPENCLAW_CLOUD_REGION — region identifier (e.g. us-east-1)
  • OPENCLAW_CLOUD_WORKSPACE_ID — workspace UUID from the console
  • OPENCLAW_WEBHOOK_SIGNING_SECRET — verify inbound events from OpenClaw Cloud
  • NEXT_PUBLIC_APP_URL — public origin of this HappyClaw deployment (for callbacks and allowlists)

Authenticate API requests

Send the workspace key on every server-to-server call:

Authorization: Bearer <OPENCLAW_CLOUD_API_KEY>

Webhooks (OpenClaw Cloud → your backend)

Register an HTTPS endpoint in the console. OpenClaw Cloud POSTs signed JSON payloads for connector events, job state, and policy updates. Reject requests with invalid signatures; use idempotent handlers because retries are expected on failure or slow consumers.

CLI & automation

Use the OpenClaw Cloud CLI from CI/CD with the same API key (scoped to a service account where possible). Rotate credentials and narrow scopes before promoting changes to production.