api-integration
Designs event-driven architectures, webhook systems, API chaining flows, ETL pipelines, and integration patterns between services.
API Integration Skill
When to Use
Use this skill when you need designs event-driven architectures, webhook systems, API chaining flows, ETL pipelines, and integration patterns between services. Use whenever the user asks about webhooks, event streaming, API composition, connecting two or more APIs, building pipelines, Pub/Sub, Kafka topics, ETL...
Design integration patterns, webhook flows, event pipelines, and API composition strategies.
Webhook Design
Outbound Webhook Endpoint (from your system to 3rd party)
POST {subscriber_url}
Headers:
Content-Type: application/json
X-Webhook-Signature: hmac-sha256=<sig>
X-Webhook-Event: order.created
X-Webhook-Delivery: <uuid>
X-Webhook-Timestamp: <unix-epoch>
Payload envelope
{
"event": "order.created",
"delivery_id": "uuid",
"created_at": "ISO8601",
"data": { ... }
}
Signature verification (receiver side):
import hmac, hashlib
expected = hmac.new(secret.encode(), payload_bytes, hashlib.sha256).hexdigest()
assert f"sha256={expected}" == request.headers["X-Webhook-Signature"]
Inbound Webhook Registration API
POST /api/v1/webhooks — register subscriber URL + events
GET /api/v1/webhooks — list subscriptions
DELETE /api/v1/webhooks/{id} — unsubscribe
POST /api/v1/webhooks/{id}/test — fire test event
GET /api/v1/webSubscribers only
The full skill, its 1 bundled files and every download is included with every paid Complete AI plan.
Details
| Source | LambdaTest/agent-skills |
|---|---|
| License | MIT |
| Risk label | none ("critical" means the skill may run commands or touch files — read before use) |
| Files | SKILL.md |
| Added | 2026-07-01 |
Related skills
api-analyzer
Validates whether an API request is correct based on provided inputs (method, URL, headers, body, auth, query params).
api-and-interface-design
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
api-design-principles
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers and stand the test of time.
api-designer
Generates complete, production-ready REST API endpoint specifications for any system or domain the user describes.
api-documentation-generator
Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices
api-documenter
Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals.
