ZARZOOM for Openclaw

1. Create a ZARZOOM developer API key at https://zarzoom.com/dashboard/api-keys.
2. Add the key to the OpenClaw configuration and enable the skill:

mkdir -p ~/.openclaw
# Edit ~/.openclaw/openclaw.json and add the zarzoom skill entry

{
  skills: {
    entries: {
      "zarzoom": {
        enabled: true,
        apiKey: {
          source: "env",
          provider: "default",
          id: "ZARZOOM_API_KEY"
        },
        env: {
          ZARZOOM_API_KEY: "zarz_live_..."
        }
      }
    }
  }
}

3. Alternatively, export the required environment variable in the runtime that launches OpenClaw:

export ZARZOOM_API_KEY="zarz_live_..."

4. Confirm that the key has access to the required scopes, including api:read:content, api:read:status, and api:write:content where applicable.
5. Connect the desired social accounts in ZARZOOM, then use the skill to discover available platforms before the first submission.
6. Keep in mind the default limits: 60 read requests per minute per key and 40 write submissions per day per workspace. On HTTP 429, use the X-RateLimit-Reset timestamp instead of retrying blindly.
7. If the key is missing, revoked, or malformed, the skill must refuse API calls and direct the user to https://zarzoom.com/dashboard/api-keys.

API conventions

Content and media records

• Articles use title, HTML body, optional image_keys, matching image_alts, up to 10 hashtags, and optional selected_platforms. The body supports up to 20,000 characters after HTML stripping and 3,000 words.
• Shorts use text, an optional single image_key, up to 10 hashtags, and optional selected platforms. Text must contain 50–150 words.
• Videos use video_key, caption, optional duration_seconds, thumb_key, hashtags, and selected platforms. Videos support MP4 or WebM, up to 100 MB and 60 seconds; captions support up to 2,200 characters.
• Images use JPEG, PNG, or WebP MIME types, up to 30 MB per file. Upload responses provide an upload_key; the temporary upload_url and expiration timestamp are never sent in the content submission.

Submission and delivery metadata

• Submission objects include submission_id, status, content_type, timestamps, rejection details, a dashboard status URL, and per_platform_status.
• Submission statuses are pending, approved, or rejected.
• Platform status records include eligibility, reason or message, posted_at, and post_url when delivery occurs.
• Queue records include post_id, platform, delivery status, timestamps, URLs, and safe error codes such as delivery_failed.
• Lists use limit and opaque cursor pagination, with the next cursor stored at meta.next_cursor.
• Calendar items organize planned date and time, content type, status, platforms, headline, hook, angle, CTA, tone, key points, hashtags, viral strength, and video approval metadata.
• Analytics are grouped under data into time windows, totals, top-performing content, and per-platform engagement, reach, and follower metrics.
• Usage records include key scopes, expiration, IP allowlist, request totals, endpoint and daily counts, status counts, and read/write rate-limit counters.