instantly-rate-limits
Implement reliable request patterns to handle Instantly API rate limits and ensure smooth integration.
Install
mkdir -p .claude/skills/instantly-rate-limits && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/8861" && unzip -o skill.zip -d .claude/skills/instantly-rate-limits && rm skill.zipInstalls to .claude/skills/instantly-rate-limits
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Implement Instantly.ai rate limiting, backoff, and request throttlingKey capabilities
- →Implement exponential backoff with jitter for API requests
- →Manage request queues with configurable concurrency
- →Throttle email listing requests to 20 per minute
- →Execute batch lead creation operations
- →Handle 429 rate limit errors
How it works
The skill provides a backoff wrapper that catches 429 and 5xx errors, applying a delay with jitter before retrying. It also includes a queue class to manage concurrency and a throttler for specific endpoints.
Inputs & outputs
When to use instantly-rate-limits
- →Handling 429 rate limit errors
- →Implementing exponential backoff with jitter
- →Optimizing API polling for background jobs
- →Managing email list request throughput
- →Building reliable webhook listeners
About this skill
Instantly Workspace Rate Control
Overview
Coordinate traffic across clients and keys so retries do not amplify throttling or duplicate writes. Record assumptions, evidence, approval state, and rollback ownership so another operator can reproduce the result.
Prerequisites
- The target repository, Instantly workspace, environment, and accountable owner
- Current security, privacy, compliance, capacity, and change-control requirements
- An approved API v2 key only when a bounded live verification is necessary
Tool Discipline
Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current first-party Instantly documentation and package metadata. Use Write or Edit only when implementation was requested and exact target files are known; never write credentials, lead data, email content, or unrestricted environment output.
Current Contract
- General limits are 100 requests per second and 6,000 per minute across API v1/v2 for the whole workspace.
- GET /emails is limited to 20 requests per minute; other endpoints may publish independent limits.
- 429 is the authoritative throttling signal; retry timing must follow documented or observed response metadata.
Authentication
Use an API v2 key as Authorization: Bearer <key> against https://api.instantly.ai/api/v2. Grant only the endpoint-specific scopes needed, inject the key from an approved server-side secret manager, and never print, persist, commit, or place it in a URL. Treat key creation, rotation, revocation, member changes, workspace delegation, and production access as owner-approved actions.
Instructions
- Inventory every producer sharing the workspace and every endpoint-specific override.
- Allocate a workspace request budget below both general windows.
- Centralize token-bucket state and expose queue depth, wait time, and 429 telemetry.
- Retry only operations proven safe, with bounded exponential backoff and jitter.
- Do not assume a webhook retry count or timing absent a published contract.
- Test burst, sustained, override, and retry-storm scenarios with synthetic traffic.
Approval Boundaries
Do not create, rotate, reveal, or revoke keys; invite or remove members; delegate across workspaces; connect sending accounts; create or activate campaigns; import or delete leads; change suppression or retention; register, patch, resume, or delete webhooks; alter plans or paid capacity; transmit diagnostics; or perform another production mutation without explicit approval from the accountable owner. Keep diagnosis read-only unless implementation was requested.
Output
Return the workspace-safe scope, files and contracts inspected, exact API v2 routes and required scopes, evidence collected, validation result, sensitive fields redacted, remaining risk, accountable owner, approval state, and rollback or next action.
Error Handling
| Condition | Response |
|---|---|
401 | Stop and verify that the bearer key exists, is current, and was not revoked. |
403 | Stop and compare the operation with its exact required scope; do not broaden to all:all by default. |
429 | Coordinate the workspace-wide budget, honor endpoint overrides, and bound retries. |
| Schema or tenant mismatch | Fail closed, preserve redacted evidence, and do not retry a mutation. |
Examples
Use a compact handoff that makes scope, mutation authority, and evidence reviewable.
Input:
workspace-rps=80; workspace-rpm=4800; email-list-rpm=15
Expected handoff:
limits=enforced; retry-budget=bounded; mutation-retries=disabled
Resources
When not to use it
- →When exceeding 20 requests per minute on the email listing endpoint
- →When ignoring standard REST limits on non-email endpoints
Prerequisites
Limitations
- →Email listing endpoint is strictly limited to 20 requests per minute
- →Webhook delivery retries are limited to 3 attempts within 30 seconds
How it compares
Unlike manual retry loops, this approach incorporates jitter to prevent thundering herd problems and provides structured concurrency control.
Compared to similar skills
instantly-rate-limits side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| instantly-rate-limits (this skill) | 1 | 2mo | Review | Intermediate |
| graphql | 6 | 8mo | No flags | Advanced |
| generating-grpc-services | 1 | 2mo | Review | Advanced |
| idmp | 0 | 4mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
graphql
davila7
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.
generating-grpc-services
jeremylongshore
Generate gRPC service definitions, stubs, and implementations from Protocol Buffers. Use when creating high-performance gRPC services. Trigger with phrases like "generate gRPC service", "create gRPC API", or "build gRPC server".
idmp
ha0z1
Use when you need to deduplicate concurrent or repeated async calls, prevent duplicate API requests, cache async function results, add automatic retry with exponential backoff, memoize heavy computation wrapped in Promise, replace SWR/Provider for request sharing, invalidate cache with flush, or per
fastapi-templates
wshobson
Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.
android-kotlin-development
aj-geddes
Develop native Android apps with Kotlin. Covers MVVM with Jetpack, Compose for modern UI, Retrofit for API calls, Room for local storage, and navigation architecture.
fastapi-pro
sickn33
Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and Pydantic V2. Master microservices, WebSockets, and modern Python async patterns. Use PROACTIVELY for FastAPI development, async optimization, or API architecture.