api-consumption

What problem does it solve?

Consuming third-party APIs and processing incoming webhooks reliably is error-prone due to network failures, rate limits, slow responses, duplicate deliveries, and tight coupling to provider SDKs. This Skill provides patterns and concrete rules to avoid timeouts, duplicate side effects, service outages, and maintain testable, replaceable service abstractions.

Core Features & Use Cases

• Typed HTTP client with configurable timeouts, retries with exponential backoff and jitter, and per-operation policies.
• Resilience patterns: circuit breaker, rate limiter, and operation-level timeouts to protect downstream services.
• Service abstraction & idempotency: encapsulate SDKs in typed services, map provider types to internal models, and use idempotency keys for safe retries.
• Webhook handling: signature verification, immediate acknowledgement, and asynchronous, idempotent processing.
• Use Case: Build a payment integration that retries safely, avoids duplicate charges via idempotency keys, enforces rate limits, and falls back when a payment provider circuit is open.

Quick Start

Create a typed HTTP client with timeout, exponential backoff retry, circuit breaker, idempotency keys, and webhook signature verification for consuming a third-party payment API.