How to Connect LINE WORKS to an AI Agent
Auth setup
1. LINE WORKS Developer Console > App登録. 2. Service Account発行 + Private Key ダウンロード. 3. JWTを生成 (iss=client_id, sub=service_account_id). 4. POST /token with grant_type=urn:ietf:params:oauth:grant-type:jwt-bearer.
Key facts
| Base URL | https://www.worksapis.com/v1.0/ |
|---|
| API version | v1.0 (API 2.0) |
|---|
| Auth | OAuth 2.0 with JWT assertion. Service account issues JWT, exchanges for access token. Developer Console for client_id and service account. |
|---|
| Token URL | https://auth.worksmobile.com/oauth2/v2.0/token |
|---|
| Scopes | bot, user.read, calendar, directory |
|---|
| Request body | application/json |
|---|
| Pagination | Cursor-based: responseMetaData.nextCursor in response. |
|---|
| Rate limit | 200 req/sec per app. Messaging: 5,000 messages/day for free plan. |
|---|
| Error format | JSON: {"code":"UNAUTHORIZED","description":"..."} |
|---|
Key endpoints
| Method | Path | Description |
|---|
POST | /bots/{botId}/channels/{channelId}/messages | Send message via Bot |
GET | /users/{userId} | Get user info |
GET | /users/{userId}/calendar/events | List calendar events |
POST | /bots/{botId}/channels/{channelId}/messages/push | Push message to channel |
Quickstart
POST /v1.0/bots/{botId}/channels/{channelId}/messages
Authorization: Bearer {access_token}
Content-Type: application/json
{"content":{"type":"text","text":"Hello from agent"}}
Agent pitfalls & tips
- JWT auth is mandatory for API 2.0 — no simple API key option.
- Private key must be RSA 2048-bit. Use jsonwebtoken library to sign JWTs.
- Bot must be registered and added to channels before sending messages.
- Access tokens expire in 24 hours — refresh proactively.
- JP企業でSlackの代替として導入されている。Messaging APIのパターンはLINE Botに類似。
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 LINE WORKS's AEO score?
▼
LINE WORKS 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 LINE WORKS AI-agent-ready?
▼
LINE WORKS 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 LINE WORKS compare to other Communication services?
▼
In the Communication category, LINE WORKS 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 LINE WORKS compares.
How can I integrate LINE WORKS with an AI agent?
▼
The fastest way to integrate LINE WORKS 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 LINE WORKS?
▼
OAuth 2.0 with JWT assertion. Service account issues JWT, exchanges for access token. Developer Console for client_id and service account. Setup: 1. LINE WORKS Developer Console > App登録. 2. Service Account発行 + Private Key ダウンロード. 3. JWTを生成 (iss=client_id, sub=service_account_id). 4. POST /token with grant_type=urn:ietf:params:oauth:grant-type:jwt-bearer.
What are LINE WORKS's API rate limits?
▼
200 req/sec per app. Messaging: 5,000 messages/day for free plan.