instantly-rate-limits

Featured

Implement Instantly.ai rate limiting, backoff, and request throttling patterns. Use when handling 429 errors, implementing retry logic, or building high-throughput Instantly integrations. Trigger with phrases like "instantly rate limit", "instantly 429", "instantly throttle", "instantly backoff", "instantly retry".

AI & Automation 2,274 stars 319 forks Updated today MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Instantly Rate Limits ## Overview Handle Instantly API v2 rate limits. The API returns `429 Too Many Requests` when limits are exceeded. Most endpoints follow standard limits. The email listing endpoint has a stricter constraint of **20 requests per minute**. Failed webhook deliveries are retried up to **3 times within 30 seconds**. ## Prerequisites - Completed `instantly-install-auth` setup - Understanding of exponential backoff patterns ## Known Rate Limits | Endpoint | Limit | Notes | |----------|-------|-------| | Most API endpoints | Standard REST limits | Varies by plan | | `GET /emails` | 20 req/min | Stricter — email listing | | Webhook deliveries | 3 retries in 30s | Instantly retries to your endpoint | | Background jobs | N/A | Async — poll via `GET /background-jobs/{id}` | ## Instructions ### Step 1: Exponential Backoff with Jitter ```typescript import { InstantlyApiError } from "./src/instantly/client"; interface RetryOptions { maxRetries: number; baseDelayMs: number; maxDelayMs: number; } const DEFAULT_RETRY: RetryOptions = { maxRetries: 5, baseDelayMs: 1000, maxDelayMs: 30000, }; async function withBackoff<T>( operation: () => Promise<T>, opts: Partial<RetryOptions> = {} ): Promise<T> { const { maxRetries, baseDelayMs, maxDelayMs } = { ...DEFAULT_RETRY, ...opts }; for (let attempt = 0; attempt <= maxRetries; attempt++) { try { return await operation(); } catch (err) { const isRetryable = err instanceof ...

Details

Author
jeremylongshore
Repository
jeremylongshore/claude-code-plugins-plus-skills
Created
7 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

customerio-rate-limits

Implement Customer.io rate limiting and backoff. Use when handling high-volume API calls, implementing retry logic, or hitting 429 errors. Trigger: "customer.io rate limit", "customer.io throttle", "customer.io 429", "customer.io backoff", "customer.io too many requests".

2,274 Updated today
jeremylongshore
AI & Automation Featured

intercom-rate-limits

Handle Intercom API rate limits with backoff, queuing, and header monitoring. Use when handling 429 errors, implementing retry logic, or optimizing API request throughput for Intercom. Trigger with phrases like "intercom rate limit", "intercom throttling", "intercom 429", "intercom retry", "intercom backoff", "intercom request limit".

2,274 Updated today
jeremylongshore
AI & Automation Featured

fireflies-rate-limits

Implement Fireflies.ai rate limiting, backoff, and request queuing. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for Fireflies.ai. Trigger with phrases like "fireflies rate limit", "fireflies throttling", "fireflies 429", "fireflies retry", "fireflies backoff".

2,274 Updated today
jeremylongshore
AI & Automation Featured

notion-rate-limits

Manage Notion API rate limits with exponential backoff, queue-based throttling, and batch optimization. Use when hitting 429 errors, implementing retry logic, or optimizing API request throughput for Notion integrations. Trigger with "notion rate limit", "notion 429", "notion retry", "notion backoff", "notion throttling", "notion too many requests", "notion queue".

2,274 Updated today
jeremylongshore
AI & Automation Featured

klaviyo-rate-limits

Implement Klaviyo rate limiting, backoff, and request queuing patterns. Use when handling 429 errors, implementing retry logic, or optimizing API request throughput for Klaviyo. Trigger with phrases like "klaviyo rate limit", "klaviyo throttling", "klaviyo 429", "klaviyo retry", "klaviyo backoff", "klaviyo Retry-After".

2,274 Updated today
jeremylongshore