Skip to content
Back to skills

Api Integration

ASecurity

Design and implement APIs, external integrations, webhooks, clients, and service boundaries using technology-agnostic principles.

  • 3 stars
  • 0 votes
  • 1 copy
  • 2 views
  • Added September 2, 2026
ai-agentsapi

Works with

  • cli
  • api

Security analysis

A100/100

Scanned September 2, 2026

npx -y skills add soden46/engineer-flow --skill api-integration --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Api Integration?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Api Integration
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/soden46-api-integration/badge)](https://www.skillsdirectory.com/skills/soden46-api-integration)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: api-integration
description: Design and implement APIs, external integrations, webhooks, clients, and service boundaries using technology-agnostic principles.
metadata:
  internal: true
---

# api-integration

Use this skill for APIs, HTTP clients, webhooks, third-party integrations, service communication, pagination, retries, and integration boundaries.

## Principles

Define explicit contracts for requests, responses, errors, and side effects.

Validate data crossing external boundaries.

Distinguish transport concerns from business logic.

For outbound calls consider:

- timeouts
- retries
- retry safety
- idempotency
- rate limits
- pagination
- partial failure
- authentication
- observability

Do not retry non-idempotent operations blindly.

For webhooks consider:

- authenticity
- replay protection when required
- duplicate delivery
- idempotent handling
- failure recovery

Keep provider-specific assumptions isolated where practical.

Do not leak transport-specific details throughout unrelated application code.

## Adaptation

Use project evidence to determine the actual language, framework, runtime, and existing conventions.

When stack-specific implementation guidance is needed, prefer project evidence, native framework or language mechanisms, and relevant user-installed specialist skills. Technology-specific guidance must not redefine or weaken the core engineering requirement.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…