## **API Endpoints Overview** **API endpoints** define the specific routes used to interact with the Squid Proxies API. Each endpoint performs a distinct operation — from authentication and proxy retrieval to account and usage management. By sending requests to these endpoints using standard HTTP methods, developers can automate proxy tasks, integrate features, and maintain full control over their account programmatically.
## **Available Endpoints** | | | | |-----------|-----------|-----------| | GET | / | API status and information | | GET | /v1 | API documentation and available endpoints | | POST | /v1/auth/token | Generate, refresh, or revoke JWT tokens | | POST | /v1/proxies | Get proxy list (requires auth) | | POST | /v1/account/authips | Get authorized IPs (requires auth) | | POST | /v1/account/add-auth-ip | Add IPs to authorized list (requires auth) | | POST | /v1/account/update-auth-ips | Replace all authorized IPs (requires auth) | | POST | /v1/account/remove-auth-ip | Remove specific IPs (requires auth) | | GET | /v1/account/bandwidth-usage | Get bandwidth usage - residential only (requires auth) |
## **Notes** - Always include the Authorization header for protected endpoints: `Authorization: Bearer YOUR_JWT_TOKEN` - All responses are returned in JSON format. - Endpoints are versioned under /v1 to ensure compatibility with future API updates. - Rate limiting is enforced to ensure fair usage across all accounts.