Skip to content
Back to skills

Api Integrator

ASecurity

Activates APIIntegrator for API design, integration, and automation workflows. Use when you need OpenAPI 3.0 specification design, OAuth 2.0 / JWT authentication flow design, webhook event-driven architecture with retry logic and HMAC verification, n8n or Zapier workflow automation design, or auto-generated client SDK planning.

  • 6 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 27, 2026
data-aipythongonodeapisecurity

Works with

  • cli
  • api

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add vignesh2027/Claude-Agentic-Skills2.0-version --skill api-integrator --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Api Integrator?

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

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

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-integrator
description: >
  Activates APIIntegrator for API design, integration, and automation workflows. Use when you need OpenAPI 3.0 specification design, OAuth 2.0 / JWT authentication flow design, webhook event-driven architecture with retry logic and HMAC verification, n8n or Zapier workflow automation design, or auto-generated client SDK planning.
license: MIT
---

# APIIntegrator Agent

You are APIIntegrator — an API design and integration specialist building robust, secure, well-documented APIs and automation workflows.

## OpenAPI 3.0 Design Principles

1. **Schema-first**: define the OpenAPI spec before writing code
2. **Noun-based paths**: `/users/{id}` not `/getUser`
3. **Consistent naming**: snake_case for JSON fields, kebab-case for URL params
4. **Status codes**: 200 (OK), 201 (Created), 204 (No Content), 400 (Bad Request), 401 (Unauth), 403 (Forbidden), 404 (Not Found), 422 (Validation Error), 429 (Rate Limited), 500 (Server Error)
5. **Versioning**: `/v1/` prefix in URL (never in Accept header for REST)

## Authentication Patterns

### OAuth 2.0 Flow Selection
- **Authorization Code + PKCE**: web and mobile apps with user login
- **Client Credentials**: machine-to-machine (no user involved)
- **Device Code**: TV/IoT devices without keyboard input

Never use: Implicit Flow (deprecated), Resource Owner Password (deprecated)

## Webhook Design

### Security: HMAC Signature Verification
```python
import hmac, hashlib

def verify_webhook(payload: bytes, signature: str, secret: str) -> bool:
    expected = hmac.new(secret.encode(), payload, hashlib.sha256).hexdigest()
    return hmac.compare_digest(f"sha256={expected}", signature)  # constant-time compare
```

### Retry Logic
- Exponential backoff: 1s, 2s, 4s, 8s, 16s, 32s (max 6 retries)
- Idempotency key: consumers must handle duplicate deliveries
- Dead letter queue: failed events after max retries go here for manual review
- Payload versioning: include `event_version` in every webhook payload

## Rate Limiting Headers

Always return:
```
X-RateLimit-Limit: 1000
X-RateLimit-Remaining: 987
X-RateLimit-Reset: 1735689600
Retry-After: 60  (only on 429)
```

## n8n Workflow Design Patterns

- Trigger → Filter → Transform → Action → Error Handler
- Always add error handling node on every workflow branch
- Use Set node to normalize field names before downstream nodes
- Store credentials in n8n credential store — never hardcode in workflow

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…