Assign many accounts to a proxy pool
Binds many accounts to a proxy pool in one call so a workspace's accounts start using its proxies. Each account is bound to the pool and the specific proxy is chosen automatically on first use, so you never pick a session. An account already bound to the pool is left as is, and an account bound to a different pool is moved to this one. An account pinned to a different pool is left untouched and excluded from the count instead; unpin it first. The response reports how many accounts are now bound to the pool.
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://loading/proxies.v1.Proxies/BulkAssignAccountsToPool" \ -H "Content-Type: application/json" \ -d '{ "poolId": "AY+MISIifMyN3T09PT09PQ==", "accountNames": [ "steam_bot_01", "steam_bot_02", "steam_bot_03" ] }'{
"assignedCount": 3
}{
"code": "failed_precondition",
"message": "The request cannot be carried out in the current system state."
}{
"code": "unauthenticated",
"message": "The request lacks a valid API key in the Authorization header."
}{
"code": "permission_denied",
"message": "The API key is not allowed to perform this action on this workspace."
}{
"code": "not_found",
"message": "The requested resource does not exist in this workspace."
}{
"code": "resource_exhausted",
"message": "The request was rate limited. Slow down and retry later."
}{
"code": "internal",
"message": "An internal server error occurred."
}{
"code": "unavailable",
"message": "The service is temporarily unavailable. Retry with backoff."
}UpdateProxyPool
Updates a legacy proxy pool's name or description. Only the fields you supply are changed. Concurrency is guarded server-side on the row's own version, so no client-supplied version is needed.
BulkCreateAssignment
Binds many accounts to proxy sessions in one call. Each row is committed independently and the response reports per-row success or a typed error, so one bad row does not fail the whole batch. The operation is idempotent per account: a row whose account is already bound to the same pool converges on the existing assignment as a no-op success, while a row whose account is already bound to a different pool reports ALREADY_EXISTS.