openapi-api
OpenAPI client and app API wiring. Use when adding or using API endpoints, editing the openapi client, or wiring new APIs in the app.
Works with
---
name: openapi-api
description: OpenAPI client and app API wiring. Use when adding or using API endpoints, editing the openapi client, or wiring new APIs in the app.
license: MIT
---
# OpenAPI and API
**Client:** The **openapi** folder holds the generated API client (do not edit by hand; regenerate from the OpenAPI spec). All API classes and types live there.
**Wiring:** **api.ts** is the single place that instantiates and exports API clients. It creates one **Configuration**, one Axios instance, and a **url** (e.g. **process.env.EXPO_PUBLIC_API_URL**). Each API class is constructed with **(config, url, axiosInstance)** and exported (e.g. **authApi**, **usersApi**).
* When the spec or generator adds a new API, add the same pattern in **api.ts**: import the **XxxApi** class, **new XxxApi(config, url, axiosInstance)**, then **export { ..., xxxApi }**.
## Usage
* Import API instances from **~/src/api** (e.g. **authApi**, **usersApi**). Call the generated methods (e.g. **authApi.signInAPI(...)**); auth is usually passed per call (e.g. token as last argument) where required.
* Most API calls are made inside **Zustand stores**; some are used directly in screens or components. Use **ErrorGet** from **~/src/scripts/error** and **Toast** for user-facing errors.More API Design skills
lark-event
larksuite/cli
Lark/Feishu real-time event listening / subscribing / consuming: stream events as NDJSON via `lark-cli event consume <EventKey>` (covers IM messages/reactions/chat changes, Approval status changes, Task updates, VC meeting started/joined/ended, Minutes generated, Whiteboard updated, etc.). Use for Lark bots, real-time message processing, long-running subscribers, streaming webhook/push handlers. Supports `--max-events` / `--timeout` bounded runs and a stderr ready-marker contract — designed for AI agents running as subprocesses.
lark-contact
larksuite/cli
飞书 / Lark 通讯录:按姓名 / 邮箱解析成 open_id,或按 open_id 反查姓名 / 部门 / 邮箱 / 联系方式 / 个人状态 / 签名,以及按关键词搜索当前用户可见的机器人 / 智能体(agent)。当用户提到一个名字要下一步发消息 / 排日程,或拿到 open_id 想查具体信息时使用。不负责部门树遍历、按部门列员工、组织架构图,这类需求走原生 OpenAPI。
lark-openapi-explorer
larksuite/cli
飞书/Lark 原生 OpenAPI 探索:从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark-* skill 或 lark-cli 已注册命令满足,需要查找并调用原生飞书 OpenAPI 时使用。

