Default Proxy Users cannot have ACL rules applied and have access to all proxies on your account.
Overview
The process involves two steps:- Create a proxy user with
proxy_user_access_type: "proxy_restricted" - Create Proxy User ACL entries to grant access to specific individual proxies
Key Points
1. Access Type Must Be Set
When creating the proxy user, you must setproxy_user_access_type to "proxy_restricted":
2. ACL Entries Grant Individual Proxy Access
After creating the proxy user, create one ACL entry for each individual proxy they should access:3. One ACL Per Proxy
Unlike service-restricted access (where one ACL grants access to all proxies in a service), proxy-restricted requires one ACL entry per proxy:- ACL 1:
customer_001→ Proxy550e8400-e29b-41d4-a716-446655440001 - ACL 2:
customer_001→ Proxy550e8400-e29b-41d4-a716-446655440002 - ACL 3:
customer_001→ Proxy550e8400-e29b-41d4-a716-446655440003
Comparison with Service-Restricted
| Feature | Service-Restricted | Proxy-Restricted |
|---|---|---|
| Grants access to | All proxies in a service | Specific individual proxies |
| ACLs needed | One per service | One per proxy |
| Best for | Team/department access | Reselling, dedicated assignments |
| Granularity | Service level | Proxy level |
| Scalability | Better for large proxy pools | Better for small, specific sets |
Verifying Access
After setup, you can verify the ACL entries were created:Managing Access
Adding More Proxies
Create additional ACL entries to grant access to more proxies:Removing Proxy Access
Delete an ACL entry to revoke access to a specific proxy:Retrieving Proxy IDs
To get proxy IDs for creating ACLs, use the proxy search endpoint:proxy_id field you can use for creating ACL entries.
