Question

You are writing a Python script that consumes a Cisco Catalyst Center REST API endpoint to build an inventory report of all managed devices. During testing you discover the API returns only 500 devices per call and intermittently responds with HTTP 429. Your organization requires the script to retrieve the complete device list reliably without being throttled. Which approach correctly handles both constraints?

Accepted Answer

Loop through the results using the 'offset' and 'limit' query parameters to page through all records, and on HTTP 429 responses read the 'Retry-After' header to back off before retrying the same request.

Answer

Increase the 'limit' query parameter to a very large value so a single request returns every device, avoiding both pagination and rate limiting.

Answer

Catch HTTP 429 responses and immediately re-issue the request in a tight loop until it succeeds, ignoring pagination since the first page contains all critical devices.

Answer

Open concurrent threads that each request a different page simultaneously to fetch all devices faster, and treat HTTP 429 as a fatal error that stops the script.