Logz.io · Arazzo Workflow

Logz.io Sub Account Cleanup

Version 1.0.0

List sub accounts, fetch one by id to confirm, and delete it.

1 workflow 1 source API 1 provider
View Spec View on GitHub ObservabilityLoggingMetricsTracingSIEMELKElasticsearchOpenSearchPrometheusGrafanaOpenTelemetryAIOpsCloud ObservabilityManaged ELKCost ManagementArazzoWorkflows

Provider

logz-io

Workflows

cleanup-subaccount
Confirm a sub account exists and then delete it.
Lists time-based accounts, retrieves the target account by id, and deletes it.
3 steps inputs: accountId, apiToken outputs: deletedAccountId
1
listAccounts
Retrieve settings for the main account and all of its sub accounts so the target account can be confirmed to exist.
2
getAccount
Read the targeted sub account by id to confirm it exists before deleting it.
3
deleteAccount
Delete the confirmed sub account by its id.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Logz.io Sub Account Cleanup
  summary: List sub accounts, fetch one by id to confirm, and delete it.
  description: >-
    Safely decommissions a logging sub account. The workflow lists all
    time-based accounts from the main account token, reads the targeted account
    by id to confirm it exists before any destructive action, then deletes the
    sub account. 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: logzioApi
  url: ../openapi/logz-io-api-openapi.yml
  type: openapi
workflows:
- workflowId: cleanup-subaccount
  summary: Confirm a sub account exists and then delete it.
  description: >-
    Lists time-based accounts, retrieves the target account by id, and deletes
    it.
  inputs:
    type: object
    required:
    - apiToken
    - accountId
    properties:
      apiToken:
        type: string
        description: Logz.io main-account API token sent in the X-API-TOKEN header.
      accountId:
        type: integer
        description: ID of the sub account to delete.
  steps:
  - stepId: listAccounts
    description: >-
      Retrieve settings for the main account and all of its sub accounts so the
      target account can be confirmed to exist.
    operationId: getAll
    parameters:
    - name: X-API-TOKEN
      in: header
      value: $inputs.apiToken
    successCriteria:
    - condition: $statusCode == 200
  - stepId: getAccount
    description: >-
      Read the targeted sub account by id to confirm it exists before deleting
      it.
    operationId: get
    parameters:
    - name: X-API-TOKEN
      in: header
      value: $inputs.apiToken
    - name: id
      in: path
      value: $inputs.accountId
    successCriteria:
    - condition: $statusCode == 200
  - stepId: deleteAccount
    description: >-
      Delete the confirmed sub account by its id.
    operationId: deleteTimeBasedAccount
    parameters:
    - name: X-API-TOKEN
      in: header
      value: $inputs.apiToken
    - name: id
      in: path
      value: $inputs.accountId
    successCriteria:
    - condition: $statusCode == 204
  outputs:
    deletedAccountId: $inputs.accountId

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/logz-io-subaccount-cleanup-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.