webhook-development
>
Works with
---
name: webhook-development
description: >
license: MIT
---
# Webhook Development
## Table of Contents
- [Overview](#overview)
- [When to Use](#when-to-use)
- [Quick Start](#quick-start)
- [Reference Guides](#reference-guides)
- [Best Practices](#best-practices)
## Overview
Build reliable webhook systems with event delivery, signature verification, retry logic, and dead-letter handling for asynchronous integrations.
## When to Use
- Sending real-time notifications to external systems
- Implementing event-driven architectures
- Integrating with third-party platforms
- Building audit trails and logging systems
- Triggering automated workflows
- Delivering payment or order notifications
## Quick Start
Minimal working example:
```json
{
"id": "evt_1234567890",
"timestamp": "2025-01-15T10:30:00Z",
"event": "order.created",
"version": "1.0",
"data": {
"orderId": "ORD-123456",
"customerId": "CUST-789",
"amount": 99.99,
"currency": "USD",
"items": [
{
"productId": "PROD-001",
"quantity": 2,
"price": 49.99
}
],
"status": "pending"
},
"attempt": 1,
"retryable": true
}
```
## Reference Guides
Detailed implementations in the `references/` directory:
| Guide | Contents |
|---|---|
| [Webhook Event Schema](references/webhook-event-schema.md) | Webhook Event Schema |
| [Node.js Webhook Service](references/nodejs-webhook-service.md) | Node.js Webhook Service |
| [Python Webhook Handler](references/python-webhook-handler.md) | Python Webhook Handler |
| [Best Practices](references/best-practices.md) | Best Practices, Webhook Events |
## Best Practices
### ✅ DO
- Follow established patterns and conventions
- Write clean, maintainable code
- Add appropriate documentation
- Test thoroughly before deploying
### ❌ DON'T
- Skip testing or validation
- Ignore error handling
- Hard-code configuration valuesMore 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 时使用。

