Skip to main content

Rate Limits

Daytona implements rate limiting to ensure platform stability and fair resource distribution across all users. Rate limits apply to all API endpoints based on your authentication method and request type.

Rate Limit Types

Daytona enforces different rate limits for different types of operations:

Authenticated Requests

Standard rate limit for authenticated API requests.
  • Limit: 100 requests per minute
  • Window: 60 seconds
  • Scope: Per API key or user token

Failed Authentication Attempts

Protects against brute-force attacks.
  • Limit: 10 failed attempts per 5 minutes
  • Window: 300 seconds
  • Scope: Per IP address

Sandbox Creation

Limits the rate of sandbox creation to prevent resource exhaustion.
  • Limit: 20 sandboxes per 10 minutes
  • Window: 600 seconds
  • Scope: Per organization

Sandbox Lifecycle Operations

Limits start, stop, restart operations on sandboxes.
  • Limit: 50 operations per 5 minutes
  • Window: 300 seconds
  • Scope: Per organization

Rate Limit Headers

Every API response includes rate limit information in the headers:
number
Maximum number of requests allowed in the time window
number
Number of requests remaining in the current window
number
Unix timestamp when the rate limit window resets

Example Response Headers

Rate Limit Errors

When you exceed a rate limit, the API returns a 429 Too Many Requests response:
number
HTTP status code (429)
string
Error message summary
string
Detailed error description
number
Seconds to wait before retrying the request

Response Headers on Rate Limit

Handling Rate Limits

Check Before Request

Monitor rate limit headers to avoid hitting limits:

Implement Exponential Backoff

Retry failed requests with exponential backoff:

Use SDK Auto-Retry

Official Daytona SDKs include automatic retry logic:

Best Practices

Use batch endpoints when available to reduce total request count:
Cache API responses when data doesn’t change frequently:
Spread requests evenly over time instead of bursting:
Track your rate limit usage over time:

Increasing Rate Limits

If your use case requires higher rate limits:
  1. Review your implementation - Ensure you’re using best practices and batch operations
  2. Contact support - Reach out to discuss your specific needs
  3. Enterprise plans - Higher rate limits available on enterprise plans
Rate limits are configurable per organization for enterprise customers. Contact sales for custom rate limit configurations.

Checking Current Limits

Retrieve your current rate limit configuration:
Response includes rate limit configuration:

Rate Limit Exemptions

Certain endpoints may be exempt from rate limiting:
  • Health check endpoints (/health, /status)
  • Public configuration endpoints (/config)
  • WebSocket connections (subject to connection limits)

Next Steps

Error Handling

Learn about all API error codes

SDKs

Use SDKs with built-in retry logic

Sandboxes API

Start making API requests

Monitoring

Monitor your API usage