api-versioning-strategies
Master API versioning techniques for backward compatibility and smooth migrations.
Works with
--- name: api-versioning-strategies description: Master API versioning techniques for backward compatibility and smooth migrations. license: Apache-2.0 --- # API Versioning Strategies Master API versioning techniques for backward compatibility and smooth migrations. ## Quick Reference ### URL Versioning ``` GET /v1/users GET /v2/users ``` ### Header Versioning ``` GET /users Accept: application/vnd.myapi.v2+json ``` ### Query Parameter ``` GET /users?version=2 ``` ### Content Negotiation ``` Accept: application/json; version=2 ``` ## Best Practices - Use semantic versioning (MAJOR.MINOR.PATCH) - Deprecate old versions with sunset warnings - Maintain at least 2 versions simultaneously - Document breaking changes clearly - Provide migration guides - Use feature flags for gradual rollout
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 时使用。
