DigitalOcean API Rate Limit: 1,000 Requests per Hour – Reset Timing and Burst Capacity Unclear

Goal

Automate a workflow that performs frequent API calls to create, modify, and delete Droplets, Images, and Kubernetes clusters. The process must remain within the documented 1,000 requests per hour limit while maintaining responsiveness.

Constraints & Uncertainty

DigitalOcean’s API reference states a default cap of 1,000 requests per hour per account, enforced per API token. When exceeded, the service returns HTTP 429 with a Retry-After header. The documentation, however, does not specify how the counter resets during a rolling window, whether a burst of requests above the average rate is tolerated, or if separate internal limits exist for specific endpoints. This ambiguity makes it difficult to design a retry strategy that guarantees completion without unnecessary delays.

Specific Questions

• How is the 1,000 requests per hour counter reset—at fixed hour boundaries, via a rolling window, or in some other manner?
• Is there an allowed burst capacity that permits short spikes above the average rate before the 429 response is triggered?
• Do individual endpoints (e.g., Droplet actions) impose additional internal limits not reflected in the global cap?