How to Connect チャネルトーク (Channel Talk) to an AI Agent
Auth setup
1. Channel Talk 管理画面 > 設定 > デベロッパー. 2. API Key (Access Key) + Secret を取得. 3. Set X-Access-Key and X-Access-Secret headers.
Key facts
| Base URL | https://api.channel.io/open/v5/ |
|---|
| API version | v5 |
|---|
| Auth | API key + secret pair. Pass as X-Access-Key and X-Access-Secret headers. Generate in Channel Talk Settings > Developer. |
|---|
| Request body | application/json |
|---|
| Pagination | Cursor-based: since/limit parameters. |
|---|
| Rate limit | Not officially documented. Observed ~100 req/sec. |
|---|
| Error format | JSON: {"type":"error","message":"..."} |
|---|
Key endpoints
| Method | Path | Description |
|---|
GET | /user-chats | List user chats (conversations) |
POST | /user-chats/{id}/messages | Send message in a chat |
GET | /users | List users/contacts |
POST | /user-chats | Create a new chat |
Quickstart
GET /open/v5/user-chats?limit=10
X-Access-Key: {access_key}
X-Access-Secret: {access_secret}
Response: {"userChats":[{"id":"...","state":"opened",...}]}
Agent pitfalls & tips
- Dual header auth: both X-Access-Key AND X-Access-Secret required.
- User chats vs team chats — user-chats are customer conversations, team-chats are internal.
- Webhook for real-time: Settings > Developer > Webhook URL.
- JP/KR market dominant — UI is in Japanese, API responses may contain JP text.
- Message types: text, file, link — check type field when parsing.
Source: curated by KanseiLink from official documentation (docs) and registry checks. Last reviewed: 2026-04-07. Specs change — verify against the official docs before production use.
Frequently Asked Questions
What is チャネルトーク (Channel Talk)'s AEO score?
▼
チャネルトーク (Channel Talk) has an AEO score of 0.60 and is rated BBB (Basic agent connectivity available). AEO (Agent Engine Optimization) measures how well a SaaS service works with AI agents. Scores range from 0.00 to 1.00, with grades from AAA (best) to D (not agent-ready).
Is チャネルトーク (Channel Talk) AI-agent-ready?
▼
チャネルトーク (Channel Talk) is currently connectable for AI agent use. API access is available but no dedicated MCP server has been published yet. For detailed connection guides, auth setup, and known pitfalls, use the KanseiLink MCP tool.
How does チャネルトーク (Channel Talk) compare to other Customer Support services?
▼
In the Customer Support category, チャネルトーク (Channel Talk) is rated BBB. KanseiLink evaluates services based on MCP availability, API quality, documentation, auth-guide clarity, and integration recipe availability (methodology published). Visit the full rankings at kansei-link.com to see how チャネルトーク (Channel Talk) compares.
How can I integrate チャネルトーク (Channel Talk) with an AI agent?
▼
The fastest way to integrate チャネルトーク (Channel Talk) with an AI agent is through KanseiLink MCP. Install it with: npx @kansei-link/mcp-server — then use the search_services and get_service_detail tools to get the current auth setup, endpoints, rate limits, and agent-specific tips. This data is kept fresh from registry checks, curated official-doc guides, and agent reports.
How do I authenticate with チャネルトーク (Channel Talk)?
▼
API key + secret pair. Pass as X-Access-Key and X-Access-Secret headers. Generate in Channel Talk Settings > Developer. Setup: 1. Channel Talk 管理画面 > 設定 > デベロッパー. 2. API Key (Access Key) + Secret を取得. 3. Set X-Access-Key and X-Access-Secret headers.
What are チャネルトーク (Channel Talk)'s API rate limits?
▼
Not officially documented. Observed ~100 req/sec.