Developer API

The ClawLink Developer API lets you run actions on your connected apps (Gmail, Slack, Instagram, Notion, and 80+ more) with plain HTTP requests. It is the same execution runtime the OpenClaw plugin and the MCP/CLI surfaces call — so anything an agent can do through ClawLink, you can do directly with curl or any HTTP client.

Base URL

https://claw-link.dev

All endpoints are JSON over HTTPS and authenticate with a cllk_live_ API key.

The mental model

ClawLink models everything as integrations → actions → executions:

Connecting an app is a hosted, browser-based flow done from the dashboard (Connections → Add connection) — there is no API to submit OAuth credentials. Once an app is connected, every execution below works against it.

Your first request

Verify your API key and see who it belongs to:

curl https://claw-link.dev/api/agent/whoami \
  -H "Authorization: Bearer cllk_live_YOUR_KEY"

{
  "user_id": "usr_123",
  "workspace_id": "usr_123",
  "workspace_name": "you@example.com",
  "environment": "production",
  "region": "global",
  "capabilities": { "can_execute": true, "can_begin_connection": true }
}

A 200 with this body means your key is valid. A 401 {"error":"Unauthorized"} means the key is missing or wrong — see Authentication.

Run an action

Send a Gmail message in one call. Write actions require confirm: true:

curl -X POST https://claw-link.dev/api/executions \
  -H "Authorization: Bearer cllk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "integration_id": "gmail",
    "action_id": "send_email",
    "input": {
      "user_id": "me",
      "to": ["sarah@example.com"],
      "subject": "Hello from the API",
      "body": "Sent directly through ClawLink."
    },
    "confirm": true
  }'

Full request/response details, the confirm field, and runnable examples for Slack and Instagram are in Executing actions.

What's in this section

Conventions

• Transport — JSON request and response bodies over HTTPS. Send Content-Type: application/json on every POST.
• Auth — every endpoint requires a cllk_live_ key (see Authentication). Unauthenticated requests get 401.
• Scope — a key acts as one ClawLink user. Executions run against that user's connections.
• Rate limits — providers (Gmail, Slack, etc.) enforce their own rate limits; ClawLink surfaces them as rate_limited / HTTP 429. Honor Retry-After where present.