Lark/Feishu API
ByteDance's enterprise collaboration suite API (Lark for international, Feishu for China) for messaging, docs, sheets, calendar, and video, with a comprehensive bot and automation platform.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Lark/Feishu collaboration platform. App ID + secret + OAuth2. Data residency considerations for US vs China regions. Scope-based permissions for messages, files, calendar.
⚡ Reliability
Best When
Your organization uses Lark or Feishu and you need AI agents to interact with team messaging, documents, and collaborative tools.
Avoid When
Your team uses Slack or Microsoft Teams — the API differences make it not worth cross-platform development.
Use Cases
- • Building Lark bots that respond to messages and send notifications from agents
- • Reading and writing Lark Docs and Sheets for document automation
- • Creating calendar events and managing meeting rooms via API
- • Sending structured Lark cards (interactive messages) from workflow agents
- • Managing user and group permissions in Lark enterprise deployments
Not For
- • Teams using Slack, Teams, or WeChat Work (switching cost is high)
- • Regions where Lark/Feishu is not commonly adopted
- • Simple webhook-only integrations (Lark has a richer but more complex bot framework)
Interface
Authentication
App access token and tenant access token. OAuth2 for user-level access. App credentials (App ID + App Secret) for bot/automation access. Lark and Feishu have separate app registries.
Pricing
Lark (international) and Feishu (China) have different pricing structures. API access is available on free plans. Enterprise features require paid plans.
Agent Metadata
Known Gotchas
- ⚠ Lark (international) and Feishu (China) have separate app platforms — apps are not cross-platform
- ⚠ Documentation is primarily in Chinese for Feishu; Lark has English docs but they can lag
- ⚠ App tokens expire frequently (2 hours) — must implement token refresh
- ⚠ Lark message cards have a proprietary JSON schema — not compatible with Block Kit or Adaptive Cards
- ⚠ Bot must be explicitly added to a group before it can send messages there
- ⚠ File upload requires a multi-step process: create upload session, upload chunks, then use file token
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Lark/Feishu API.
Scores are editorial opinions as of 2026-03-06.