api-integration

Define resilient REST contracts with OAuth2/JWT auth and retry logic.

8|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/drewid74/ai_skills --skill api-integration-drewid74
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-integration
Source: https://github.com/drewid74/ai_skills/tree/main/api-integration
Command: npx skills add https://github.com/drewid74/ai_skills --skill api-integration-drewid74

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design and implement reliable API integrations when you face auth failures (401/403), rate limiting (429), timeouts, webhook delivery issues, or inconsistent error and response formats that break clients.

Core Features & Use Cases

  • Resilient contract design: Establishes consistent request/response semantics, including status codes, pagination envelopes, and machine-readable error objects.
  • Correct authentication & security: Specifies OAuth2 + JWT patterns and secure API key handling that avoids leaking credentials in URLs or logs.
  • Practical integration behavior: Defines retry/backoff rules, idempotency requirements, and OpenAPI/Swagger specification for contract clarity and tooling support.
  • Use Case Example: Integrate a third-party REST service for creating and listing resources, while handling 429 with Retry-After, using cursor pagination for large datasets, and returning uniform error payloads your client can reliably parse.

Quick Start

Use the api-integration skill to design a REST API client and server contract that handles OAuth2/JWT authentication, correct status codes, cursor pagination, and safe retry logic for 5xx, timeouts, and 429 responses.

Frequently Asked Questions about api-integration

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

FAQPage Schema
How do I handle API rate limiting (429) and timeouts in my integration?

Handle API rate limiting by respecting 429 status codes with Retry-After headers, applying retry logic with exponential backoff and jitter for timeouts and 5xx errors, and preventing retries for 4xx client errors.

What is the best way to structure OAuth2 and JWT authentication for a REST API?

Structure OAuth2 and JWT authentication by specifying correct token patterns and secure credential placement, ensuring API keys and tokens are never leaked in URLs or application logs.

How do I design machine-readable error payloads for REST API integrations?

Design machine-readable error payloads by establishing a resilient REST contract with consistent status codes and uniform error objects that your API client can reliably parse across all responses.

Why does my API integration fail on large datasets and how do I implement cursor pagination?

API integrations fail on large datasets without pagination envelopes. Implement cursor pagination to manage sequential data fetching, ensuring consistent request and response semantics across resource lists.

Can I use OpenAPI specifications to troubleshoot webhook delivery issues?

Yes, use OpenAPI and Swagger specifications to define contract clarity and tooling support, establishing idempotency requirements and explicit timeouts that resolve inconsistent webhook delivery failures.

When should I not use exponential backoff for API error handling?

Avoid exponential backoff for 4xx client errors. Configure quality gates to prevent 4xx retries, ensuring retry logic with backoff and jitter only applies to 5xx server errors, timeouts, and 429 rate limits.