Who sits on this address
The first question after a number gets banned: which address it was on, and who else was there.
BearerAuthorizationBearer <JWT>uid*stringproxy uid
uuidThe live bindings
application/json- response
success*truetruedata*curl -X GET 'http://localhost:3000/admin/proxies/497f6eca-6276-4993-bfeb-53cbbbba6f08/bindings'{ "success": true, "data": { "bindings": [ { "accountUid": "string", "accountName": "string", "seatUid": "string", "channel": "string", "boundAt": "2019-08-24T14:15:22Z" } ] }}Change capacity, or drain and burn PATCH
`draining` stops new sessions landing here without touching the ones already on it. `burned` is for an address WhatsApp has started refusing: every session on it is ended and has to be paired again, the guardians and each dependent are told, and the accounts re-enter the sync queue ahead of the newcomers.
What is left at each provider GET
The renewal figure is an ESTIMATE: the provider exposes no charged amount anywhere, and its first purchase cost 35% more than the plan it names. `atRisk` says how many sessions fall over if those renewals do not happen, which is the number that makes anyone act. The workers read every balance hourly (`refreshEveryMinutes`); `fetchedAt`/`stale` say how old the figure is and `failingSince`/`lastError` whether the reads are failing. `shortfallCents` spends the balance on the renewals due within `horizonDays`, in date order.