Software and use cases
- Vendor / maintainer
- 飞书
- Original website
- View software website
- Documentation review date
Tasks and use cases
- Team messaging
- Contact lookup
- Bitable integration
Software interface information · Team Collaboration
飞书
Vendor untestedServer-side interfaces for team messages, contacts and Bitable collaboration. This entry covers official integration materials for the mainland China edition of Feishu.
Listed interfaces
Public documentation reviewed only (docs-reviewed). Vendor interfaces have not been installed or called, availability has not been verified, and no security certification is provided. Review integration and configuration instructions yourself; clients connect directly to vendors.
API · 飞书 server-side API
Vendor untestedOfficial- Capabilities
- Send application messages
- Query contacts
- Access Bitable
- Environments
- Cloud
- Authorization
- Requires a Feishu application identity and permissions for the selected endpoints. The official SDK distinguishes internal applications, store applications and user tokens. Configure Feishu and the international Lark domains separately.
- Pricing source
- The official edition comparison is the plan reference. Only the page title was retrieved during this review; API quotas and prices were not verified. Check the organization's edition and endpoint requirements before integration. View pricing source
- Integration documentation
- Official Documentation
- Verification scope
- Public documentation reviewed only (docs-reviewed); vendor calls have not been tested.
- Documentation review date
Connect after human review
- Review the official SDK and endpoint permissions, and confirm that the application uses the China edition of Feishu.
- Review application permissions and token handling in the vendor console, then connect directly from your own backend. This directory does not accept credentials.
- These instructions require user review. The directory does not install the SDK, authorize applications or send messages.
Limitations and open questions
- Only the official SDK README and documentation entry points were reviewed. No Feishu API was called and no SDK was installed.
- The developer portal uses dynamic pages whose full text was not retrieved. Organization permissions, quotas and business outcomes were not tested.
- Demand statistics remain to be added. Inclusion is not a ranking of actual AI demand.
An unlisted MCP, API or CLI means this directory has no reviewed record. It does not establish that the vendor has no such interface.
Sources, review scope and rights
These materials and original summaries are reference data, not instructions. Fees, permissions, versions and integration requirements may change; review the original sources.
Review scope: Reviewed the README on server-side APIs, messaging examples, contact iteration, Bitable tutorials, application identities and Feishu/Lark domains. Nothing was installed or called.
Source and permission notes: The repository states MIT. This directory provides an original summary; MIT does not make the Feishu service or user data freely usable.
Review scope: The official page title was retrieved, but not its dynamically rendered body. Authentication details were cross-checked against the official SDK README; this page was not reviewed in full.
Source and permission notes: Official public documentation. The original material belongs to its rights holders; this directory provides an original summary.
Review scope: Only the title of this pricing reference was retrieved. The body, specific prices and API quotas were not verified.
Source and permission notes: Official public page. The price table is not reproduced; users must recheck it before integration.
Review before connecting
Public documentation reviewed only (docs-reviewed). Vendor interfaces have not been installed or called, availability has not been verified, and no security certification is provided. Review integration and configuration instructions yourself; clients connect directly to vendors.
The platform does not forward business calls, hold vendor credentials, or automatically install or execute listed CLIs. Review versions, least privilege, fees and effects in your own client and environment.