Oxylabs · Arazzo Workflow

Oxylabs Sub-user Usage Audit

Version 1.0.0

Log in, list sub-users, and pull per-sub-user target statistics for an audit.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub AI Web ScrapingBot Mitigation BypassCAPTCHA SolvingData ExtractionDatacenter ProxiesDatasetsE-Commerce DataHeadless BrowserISP ProxiesMobile ProxiesProxiesResidential ProxiesSERPScraper APIScrapingWeb DataWeb IntelligenceWeb UnblockerArazzoWorkflows

Provider

oxylabs

Workflows

sub-user-usage-audit
Pull per-target statistics for a residential proxy sub-user.
Logs in, lists sub-users for scope, then reads the target statistics for the chosen sub-user.
3 steps inputs: password, subUserId, username outputs: subUsers, targetStats
1
login
Exchange the account username and password for a bearer token and the numeric account user id.
2
listSubUsers
List the account sub-users to confirm the audit scope.
3
targetStats
Read the per-target statistics for the chosen sub-user.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Oxylabs Sub-user Usage Audit
  summary: Log in, list sub-users, and pull per-sub-user target statistics for an audit.
  description: >-
    Audits residential proxy consumption at the sub-user level. The workflow
    logs in to the Residential Public API, lists the account sub-users to
    confirm the audit scope, and then reads the target statistics for a chosen
    sub-user. The target-stats read breaks consumption down by target so the
    caller can attribute traffic to specific destinations. Every step spells
    out its request inline so the flow can be read and executed without opening
    the underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: loginApi
  url: ../openapi/oxylabs-login-api-openapi.yml
  type: openapi
- name: usersApi
  url: ../openapi/oxylabs-users-api-openapi.yml
  type: openapi
workflows:
- workflowId: sub-user-usage-audit
  summary: Pull per-target statistics for a residential proxy sub-user.
  description: >-
    Logs in, lists sub-users for scope, then reads the target statistics for
    the chosen sub-user.
  inputs:
    type: object
    required:
    - username
    - password
    - subUserId
    properties:
      username:
        type: string
        description: Residential API account username for basic auth.
      password:
        type: string
        description: Residential API account password for basic auth.
      subUserId:
        type: integer
        description: Identifier of the sub-user to audit.
  steps:
  - stepId: login
    description: >-
      Exchange the account username and password for a bearer token and the
      numeric account user id.
    operationId: residentialLogin
    parameters:
    - name: Authorization
      in: header
      value: "Basic {$inputs.username}:{$inputs.password}"
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      token: $response.body#/token
      userId: $response.body#/user_id
  - stepId: listSubUsers
    description: >-
      List the account sub-users to confirm the audit scope.
    operationId: listSubUsers
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $steps.login.outputs.token"
    - name: userId
      in: path
      value: $steps.login.outputs.userId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      subUsers: $response.body
  - stepId: targetStats
    description: >-
      Read the per-target statistics for the chosen sub-user.
    operationId: getSubUserTargetStats
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $steps.login.outputs.token"
    - name: userId
      in: path
      value: $steps.login.outputs.userId
    - name: subUserId
      in: path
      value: $inputs.subUserId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      targetStats: $response.body
  outputs:
    subUsers: $steps.listSubUsers.outputs.subUsers
    targetStats: $steps.targetStats.outputs.targetStats

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/oxylabs-sub-user-usage-audit-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.