Dell Servers · Arazzo Workflow

Dell Servers OpenManage Session and Device Listing

Version 1.0.0

Authenticate to OpenManage Enterprise and list managed server devices.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub HardwareInfrastructureManagementMonitoringServersArazzoWorkflows

Provider

dell-servers

Workflows

ome-session-list-devices
Create an OME session, list server devices, then read one device.
Opens an OME API session, lists devices filtered to servers, and reads the first returned device in detail.
3 steps inputs: deviceFilter, password, userName outputs: authToken, deviceCount, serviceTag
1
createSession
{$sourceDescriptions.sessionsApi.url}#/paths/~1SessionService~1Sessions/post
Authenticate to the OME console and capture the X-Auth-Token returned for subsequent requests.
2
listDevices
List managed devices filtered to the server device type.
3
getDevice
Read the first returned device in detail.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Dell Servers OpenManage Session and Device Listing
  summary: Authenticate to OpenManage Enterprise and list managed server devices.
  description: >-
    Establishes an authenticated session with an OpenManage Enterprise console
    and enumerates the managed server devices. The workflow creates an API
    session to obtain an X-Auth-Token, then lists devices filtered to the
    server device type and reads one device in detail. Because createSession is
    declared in more than one Dell source description, the session step
    references it through the source-qualified operationPath form to remove
    ambiguity. 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
  x-realizes-capability-ids:
  - BC-600.50
  x-capability-derivation:
    method: 'deterministic join: sourceDescriptions -> per-tag OpenAPI -> tag/capability edge. No classification at this step.'
    min_confidence: 0.7
    sources:
    - capability_id: BC-600.50
      capability_name: IT Infrastructure Management
      spec: dell-servers-devices-api-openapi.yml
      confidence: 0.8
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: devicesApi
  url: ../openapi/dell-servers-devices-api-openapi.yml
  type: openapi
- name: sessionsApi
  url: ../openapi/dell-servers-sessions-api-openapi.yml
  type: openapi
workflows:
- workflowId: ome-session-list-devices
  summary: Create an OME session, list server devices, then read one device.
  description: >-
    Opens an OME API session, lists devices filtered to servers, and reads the
    first returned device in detail.
  inputs:
    type: object
    required:
    - userName
    - password
    properties:
      userName:
        type: string
        description: OpenManage Enterprise console username.
      password:
        type: string
        description: OpenManage Enterprise console password.
      deviceFilter:
        type: string
        description: >-
          OData filter expression for the device listing, for example
          Type eq 1000 for servers.
  steps:
  - stepId: createSession
    description: >-
      Authenticate to the OME console and capture the X-Auth-Token returned for
      subsequent requests.
    operationPath: '{$sourceDescriptions.sessionsApi.url}#/paths/~1SessionService~1Sessions/post'
    requestBody:
      contentType: application/json
      payload:
        UserName: $inputs.userName
        Password: $inputs.password
        SessionType: API
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      authToken: $response.header.X-Auth-Token
  - stepId: listDevices
    description: List managed devices filtered to the server device type.
    operationId: listDevices
    parameters:
    - name: X-Auth-Token
      in: header
      value: $steps.createSession.outputs.authToken
    - name: $filter
      in: query
      value: $inputs.deviceFilter
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      deviceCount: $response.body#/@odata.count
      firstDeviceId: $response.body#/value/0/Id
  - stepId: getDevice
    description: Read the first returned device in detail.
    operationId: getDevice
    parameters:
    - name: X-Auth-Token
      in: header
      value: $steps.createSession.outputs.authToken
    - name: DeviceId
      in: path
      value: $steps.listDevices.outputs.firstDeviceId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      serviceTag: $response.body#/DeviceServiceTag
      model: $response.body#/Model
      deviceHealth: $response.body#/Status
  outputs:
    authToken: $steps.createSession.outputs.authToken
    deviceCount: $steps.listDevices.outputs.deviceCount
    serviceTag: $steps.getDevice.outputs.serviceTag

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/dell-servers-ome-session-list-devices-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.