Oxylabs · Arazzo Workflow

Oxylabs Offboard Sub-user

Version 1.0.0

Read a sub-user record then delete it from the residential account.

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

offboard-sub-user
Snapshot then delete a residential proxy sub-user.
Logs in, reads the sub-user record for an audit snapshot, then deletes the sub-user.
3 steps inputs: password, subUserId, username outputs: deletedStatus, snapshot
1
login
Exchange the account username and password for a bearer token and the numeric account user id.
2
snapshotSubUser
Read the sub-user record to capture its final state before deletion.
3
deleteSubUser
Delete the sub-user from the account.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Oxylabs Offboard Sub-user
  summary: Read a sub-user record then delete it from the residential account.
  description: >-
    Removes a residential proxy sub-user safely. The workflow logs in to the
    Residential Public API, reads the sub-user record so the caller can capture
    its final state before removal, and then deletes the sub-user. Reading the
    record first gives an auditable snapshot of the sub-user prior to the
    destructive delete. 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: offboard-sub-user
  summary: Snapshot then delete a residential proxy sub-user.
  description: >-
    Logs in, reads the sub-user record for an audit snapshot, then deletes the
    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 remove.
  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: snapshotSubUser
    description: >-
      Read the sub-user record to capture its final state before deletion.
    operationId: getSubUser
    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:
      subUser: $response.body
  - stepId: deleteSubUser
    description: >-
      Delete the sub-user from the account.
    operationId: deleteSubUser
    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 == 204
    outputs:
      deletedStatus: $statusCode
  outputs:
    snapshot: $steps.snapshotSubUser.outputs.subUser
    deletedStatus: $steps.deleteSubUser.outputs.deletedStatus

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-offboard-sub-user-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.