# How to connect Just One API to OpenClaw (paste one key, 279 tools)

> Connect Just One API to OpenClaw with ClawLink: paste your Just One API key once and 279 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/openclaw/just-one-api

The usual route to Just One API access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Just One API setup: install one ClawHub skill, connect Just One API in the browser, and OpenClaw can call real Just One API actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.

## Setup

It takes three steps to connect OpenClaw to Just One API.

1. **Install ClawLink** — add the plugin to OpenClaw once.
2. **Connect Just One API** — one-click OAuth in the ClawLink dashboard.
3. **Use it from chat** — ask OpenClaw in plain English.

**Paste this into OpenClaw to set up ClawLink:**

> I want to connect my apps to OpenClaw through ClawLink.
> Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin`
> When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md

**Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead:

```bash
npx -y @useclawlink/cli login          # sign in via browser — no API key to paste
npx -y @useclawlink/cli connect just-one-api  # connect Just One API (browser OAuth)
npx -y @useclawlink/cli actions just-one-api  # list available actions
npx -y @useclawlink/cli run just-one-api <action> --input '<json>'  # execute (add --confirm for writes)
```

### Install by command

The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:

```bash
openclaw plugins install clawhub:clawlink-plugin
```

Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Just One API in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Just One API API key once.

Verify the connection by asking OpenClaw:

> Use Just One API to 1688 get item detail and walk me through the result in plain English.

### Using a different agent?

The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:

```bash
npx -y @useclawlink/cli login
```

`login` opens the same browser approval and stores a credential locally. Once Just One API is connected in the dashboard, that agent calls the same 279 Just One API tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent).

## Just One API MCP for OpenClaw

Looking for a Just One API MCP server for OpenClaw? ClawLink connects Just One API to OpenClaw and exposes 279 Just One API tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Just One API integration](https://claw-link.dev/hermes/just-one-api) works the same way.

## What the OpenClaw Just One API integration can do

279 Just One API tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 279.

### 30 of 279 Just One API tools for OpenClaw

| Tool | What it does |
|---|---|
| **1688 get item detail** `just_one_api_1688_get_item_detail` | Retrieves the public product detail for a 1688 wholesale listing by item ID |
| **1688 search item list** `just_one_api_1688_search_item_list` | Searches 1688 wholesale product listings by keyword |
| **Aliexpress get product detail** `just_one_api_aliexpress_get_product_detail` | Retrieves an AliExpress product by item ID with optional currency, region, and locale controls |
| **Aliexpress search products** `just_one_api_aliexpress_search_products` | Searches AliExpress products with optional query, page, sort, category, brand, location |
| **Amazon get best sellers** `just_one_api_amazon_get_best_sellers` | Retrieves paginated Amazon Best Sellers for a category path in a selected country marketplace |
| **Amazon get category products** `just_one_api_amazon_get_category_products` | Retrieves paginated Amazon products for a numeric category node in a selected country |
| **Amazon get product detail** `just_one_api_amazon_get_product_detail` | Retrieves details for an Amazon product identified by ASIN in a selected country marketplace |
| **Amazon get product top reviews** `just_one_api_amazon_get_product_top_reviews` | Retrieves the top reviews for an Amazon product identified by ASIN in a selected country |
| **Amazon search products** `just_one_api_amazon_search_products` | Searches Amazon marketplace products by keyword or ASIN with country, sort, condition |
| **Bilibili get user detail** `just_one_api_bilibili_get_user_detail` | Retrieves a Bilibili user profile identified by UID |
| **Bilibili get user relation stat** `just_one_api_bilibili_get_user_relation_stat` | Retrieves relation statistics for a Bilibili user identified by WMID |
| **Bilibili get user video list** `just_one_api_bilibili_get_user_video_list` | Retrieves videos published by a Bilibili user identified by UID, with an optional continuation |
| **Bilibili get video caption** `just_one_api_bilibili_get_video_caption` | Retrieves caption data for a Bilibili video segment identified by BVID, AID, and CID |
| **Bilibili get video comment** `just_one_api_bilibili_get_video_comment` | Retrieves comments for a Bilibili video identified by AID, with optional cursor pagination |
| **Bilibili get video danmu** `just_one_api_bilibili_get_video_danmu` | Retrieves one page of danmaku comments for a Bilibili video segment identified by AID and CID |
| **Bilibili get video detail** `just_one_api_bilibili_get_video_detail` | Retrieves details for a Bilibili video identified by its BVID |
| **Bilibili search video** `just_one_api_bilibili_search_video` | Searches Bilibili videos by keyword with page-based pagination and sorting by general ranking |
| **Bilibili share URL transfer** `just_one_api_bilibili_share_url_transfer` | Resolve a supported Bilibili short share link that targets a video and return its public |
| **Cross platform search** `just_one_api_cross_platform_search` | Searches cached recent content across news, Weibo, WeChat, Zhihu, Douyin, Xiaohongshu |
| **Douban get movie comments** `just_one_api_douban_get_movie_comments` | Retrieves paginated Douban short comments for a movie or TV subject, ordered by time or newest |
| **Douban get movie review detail** `just_one_api_douban_get_movie_review_detail` | Retrieves a single Douban long-form review by its review ID |
| **Douban get movie reviews** `just_one_api_douban_get_movie_reviews` | Retrieves paginated Douban long-form reviews for a movie or TV subject, ordered by time or |
| **Douban get recent hot movie** `just_one_api_douban_get_recent_hot_movie` | Retrieves a paginated list of movies currently featured in Douban's recent-hot collection |
| **Douban get recent hot tv** `just_one_api_douban_get_recent_hot_tv` | Retrieves a paginated list of TV titles currently featured in Douban's recent-hot collection |
| **Douban get subject detail** `just_one_api_douban_get_subject_detail` | Retrieves the public detail page data for a Douban movie or TV subject by subject ID |
| **Douyin ec get item comments** `just_one_api_douyin_ec_get_item_comments` | Retrieves paginated customer comments for a Douyin E-commerce product by item ID |
| **Douyin ec get item detail** `just_one_api_douyin_ec_get_item_detail` | Retrieves Douyin E-commerce product details, including sales data, by item ID |
| **Douyin ec get item sku info** `just_one_api_douyin_ec_get_item_sku_info` | Retrieves SKU information for a Douyin E-commerce product by item ID |
| **Douyin ec get shop item list** `just_one_api_douyin_ec_get_shop_item_list` | Retrieves a paginated product list for a Douyin E-commerce shop by shop ID |
| **Douyin ec search item list** `just_one_api_douyin_ec_search_item_list` | Searches Douyin E-commerce products by keyword with page and search-ID pagination |

## Example prompts

**1688 Get Item Detail**

> Use Just One API to 1688 get item detail and walk me through the result in plain English.

**1688 Search Item List**

> Search Just One API for what I need, summarize the results, and tell me the next best action.

**Aliexpress Get Product Detail**

> Use Just One API to aliexpress get product detail and walk me through the result in plain English.

**Aliexpress Search Products**

> Search Just One API for what I need, summarize the results, and tell me the next best action.

## ClawLink vs. building it yourself

The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Just One API working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Just One API API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Just One API account becomes available to the agent without you building credential management. |
| **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Just One API. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| **Agent usability** | You still need to expose the right Just One API actions to the runtime in a format your agent can reliably use. | 279 tools for Just One API are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Just One API to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Just One API in the browser, and the 279 tools above work from chat. There is no SDK and no config file, and the Just One API key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison.

### OpenClaw installed the Just One API skill but can't call the tools
The ClawHub skill teaches OpenClaw about Just One API, but the calls run through the ClawLink plugin and your connected account. Make sure Just One API is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.

### Connection succeeds but no tools appear
Reconnect Just One API from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

### "Tool schema not loaded yet" error when calling Just One API tools
Just One API tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Just One API call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.

### Just One API returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.

### API key setup works but results look incomplete
Double-check that the API key for Just One API has the right scopes or account access. A valid key can still be too limited for some reads or writes.

### Is there a OpenClaw Just One API integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Just One API: link your Just One API account once in the browser and OpenClaw can call the Just One API API through 279 ready-made tools — no custom code or token handling.

### How do I add Just One API to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Just One API skill from ClawHub, then you click Connect in the dashboard to authorize Just One API. OpenClaw calls the tools from the next message — no config files, and the Just One API key you paste is stored server-side instead of in your environment.

### How long does it take to connect Just One API to OpenClaw?
About two minutes. Sign in, click Connect next to Just One API in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

### Why use ClawLink instead of wiring Just One API up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Just One API working from chat.

### OpenClaw installed the Just One API skill but can't call the tools
The ClawHub skill teaches OpenClaw about Just One API, but the calls run through the ClawLink plugin and your connected account. Make sure Just One API is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.

## Related

- [OpenClaw DataRobot integration](https://claw-link.dev/openclaw/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
- [OpenClaw Chatbotkit integration](https://claw-link.dev/openclaw/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications.
- [Connect OpenWeb Ninja](https://claw-link.dev/openclaw/openweb-ninja) — OpenWeb Ninja provides native APIs for web search, AI answers, e-commerce, finance, jobs, maps, news, real estate, contact enrichment, traffic, and web scraping.
