Build a resilient bulk data pull from Petfinder v2 using pagination and rate-limit backoff
domain: api.petfinder.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Use the limit, up to a maximum of 100, and page query parameters on animals and organizations endpoints to page through large result sets
Read the pagination object in each response for total_pages and current_page to know when to stop
Implement exponential backoff and retry on 5xx or throttling-style errors, since Petfinder does not publish exact numeric rate-limit thresholds
Cache OAuth2 access tokens in memory for their 3600-second lifetime instead of requesting a new token per page
Log RFC 7807-style error responses, including fields like type, title, and status, to distinguish auth failures from data errors
Known gotchas
Petfinder's official docs do not state a specific requests-per-minute or per-day limit, so treat throttling as undocumented and design for graceful retry rather than a fixed quota
Large exports should still respect the maximum of 100 records per page to avoid oversized responses
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?