Throttle Sub-user Traffic
A 3-step recipe with Oxylabs. We can help you get access.
Recipe · 3 steps
Throttle Sub-user Traffic
with Oxylabs
Update a sub-user's traffic limit and status by name.
- Exchange the account username and password for a bearer token and the numeric account user id.
- List the sub-users so the caller can confirm the target sub-user exists before patching it.
- Patch the target sub-user with the new traffic limit and status.
What you'll need to have ready
- username: Residential API account username for basic auth.
- password: Residential API account password for basic auth.
- subUserId: Identifier of the sub-user to patch.
- traffic_limit: New traffic limit to apply to the sub-user.
- status: New status to apply to the sub-user (e.g. active, disabled).
For your developer
Arazzo workflow oxylabs:throttle-sub-user-traffic, 3 operations: residentialLogin → listSubUsers → updateSubUser. Specs on APIs.io.