Agent skill · software engineering · jeremylongshore
appfolio-rate-limits
Handle AppFolio API rate limits with throttling and backoff.
Why this skill is useful
Adds a complete implementation for handling AppFolio API rate limits with throttling, retries, and error handling that the AI wouldn't generate on its own.
What it needs
Requires appfolio account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
AppFolio Rate Limits Overview AppFolio's Stack API enforces per-partner rate limits to protect shared property management infrastructure. High-volume operations like bulk tenant imports, rent-roll syncs, and work-order batch updates can quickly exhaust quotas. Property managers running nightly portfolio syncs across hundreds of units must throttle carefully, especially during month-end when lease renewals and payment processing spike concurrently. Prerequisites A verified per-endpoint limit from the current AppFolio partner contract or response headers; do not rely on a generic rate value for tenant writes. Persisted batch cursors, idempotency keys for every write, and an operator policy for pausing month-end or other safety-sensitive workloads. A staging fixture and request-budget owner who can prove retries, 429 behavior, and unknown-write handling without touching production tenants. Instructions 1. Select the limiter ceiling for the specific endpoint and keep concurrency below the smallest applicable portfolio or partner limit. 2. Acquire a token before each request, honor Retry-After, and cap retries with jitter for transient provider failures. 3. Process writes from a persisted cursor with idempotency keys; never replay a tenant create just because the response was lost. 4. Pause and escalate batches that exhaust the retry budget, hit a maintenance window, or have an unknown write outcome. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/appfolio-rate-limits