Yes, a RESTful API for monitoring bandwidth usage, managing credentials, retrieving connection details, viewing analytics, and managing account settings. Available on all plan tiers.

API key authentication via Authorization: Bearer header. Key available in dashboard settings. Never expose in client-side code. All requests must use HTTPS.

Usage monitoring, credential management, account settings, and analytics (success rates, response times, geographic breakdowns). Build custom dashboards and automate provisioning.

Yes, varying by plan tier. Higher tiers get more generous limits. 429 response with Retry-After header when exceeded. Use webhooks instead of polling where possible.

Use the usage endpoint for current and historical bandwidth data. Poll every 5-15 minutes. Implement threshold alerts when usage exceeds 80% of allocation.

Rotation is controlled through proxy connection parameters (session IDs), not the API. The API handles account management and monitoring. Gateway handles real-time connections.

Integration examples for Python, Node.js, Java, Go, and PHP. RESTful API is easy to consume with any HTTP client. For proxy connections, standard HTTP proxy config works everywhere.

Standard HTTP codes: 200 success, 400 bad request, 401 auth failure, 429 rate limited, 500 server error. Implement retry with exponential backoff for 429 and 5xx. Log errors with request IDs for support.

Notification systems available for bandwidth alerts, plan expiration, and security events. More efficient than polling. Configure in dashboard.

Yes, at no additional cost. Rate limits vary by tier. Enterprise plans can receive custom API rate limits. Trial accounts also have API access.