api-connector

Generate third-party API integrations with retry mechanisms, rate limiting, and DTOs.

Updated Feb 12, 2026

Search Tags:#api #integration #resilience #dto #gateway pattern #production-grade

Ready to run

npx skills add https://github.com/hadimiftahulf/antigravity-skills --skill api-connector-hadimiftahulf

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: api-connector
Source: https://github.com/hadimiftahulf/antigravity-skills/tree/main/api-connector
Command: npx skills add https://github.com/hadimiftahulf/antigravity-skills --skill api-connector-hadimiftahulf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the creation of reliable, production-ready integrations with third-party APIs, ensuring your application can communicate effectively and resiliently.

Core Features & Use Cases

API Integration Generation: Creates service classes and DTOs for seamless data transfer.
Resilience Patterns: Implements timeouts, exponential backoff retries, and circuit breakers for stability.
Debugging Support: Includes logging for requests/responses and custom exception handling.
Use Case: Integrate a new payment gateway by defining its API endpoints, request/response structures, and implementing retry logic for failed transactions.

Quick Start

Use the api-connector skill to generate a Stripe API integration service with DTOs and retry logic.

Frequently Asked Questions about api-connector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I build a production-grade API integration with retry logic and rate limiting?▼

To build a production-grade API integration, generate service classes and DTOs that implement resilience strategies like exponential backoff retries, timeouts, and circuit breakers to ensure stable third-party communication.

What is the gateway pattern for API communication and when should I use it?▼

The gateway pattern for API communication structures data transfer through dedicated service classes and DTOs, isolating external API logic from your core application to improve maintainability and resilience against failures.

How do I implement a circuit breaker and exponential backoff for third-party API requests?▼

Implement a circuit breaker and exponential backoff by wrapping API requests in a service class that monitors failures and progressively delays retries, preventing cascading system failures during third-party outages.

Can I use this approach to integrate a new payment gateway with custom exception handling?▼

Yes, you can integrate a new payment gateway by defining its API endpoints, request and response structures, and applying custom exception handling alongside retry logic for failed transactions.

What's the best way to structure Data Transfer Objects for seamless API data transfer?▼

The best way to structure Data Transfer Objects is to define dedicated DTO classes that map request and response payloads, ensuring type safety and seamless data transfer between your application and external APIs.

Why do my API integrations fail under high load and how can I add resilience?▼

API integrations fail under high load without resilience strategies, but adding rate limiting, timeouts, and circuit breakers stabilizes communication by controlling request flow and gracefully handling third-party service degradation.