Soracom · Arazzo Workflow

Soracom Register Inventory Device to Group

Version 1.0.0

Create a Soracom Inventory device, bind it to an Inventory group, and confirm the binding.

1 workflow 1 source API 1 provider
View Spec View on GitHub IoTCellularLPWANSIMLoRaWANSigfoxMVNOConnectivityEdgeJapanArazzoWorkflows

Provider

soracom

Workflows

register-device-to-group
Create an Inventory device and attach it to an Inventory group.
Creates a device with the supplied metadata, sets its group, and reads the device to verify it now reports the target group ID.
3 steps inputs: deviceName, endpoint, groupId, manufacturer outputs: deviceId, groupId
1
createDevice
Create the Inventory device record with the supplied endpoint and manufacturer metadata and a name tag.
2
setDeviceGroup
Add the newly created device to the supplied Inventory group.
3
confirmDevice
Read the device back to confirm it now reports membership in the target group.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Soracom Register Inventory Device to Group
  summary: Create a Soracom Inventory device, bind it to an Inventory group, and confirm the binding.
  description: >-
    Onboards a LwM2M device into Soracom Inventory. The workflow creates a new
    device record (carrying endpoint and manufacturer metadata plus name tag),
    adds the device to an Inventory group so it inherits group configuration,
    and reads the device back to confirm the group binding. 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: deviceApi
  url: ../openapi/soracom-device-api-openapi.yml
  type: openapi
workflows:
- workflowId: register-device-to-group
  summary: Create an Inventory device and attach it to an Inventory group.
  description: >-
    Creates a device with the supplied metadata, sets its group, and reads the
    device to verify it now reports the target group ID.
  inputs:
    type: object
    required:
    - deviceName
    - groupId
    properties:
      deviceName:
        type: string
        description: A display name stored in the device's name tag.
      endpoint:
        type: string
        description: The LwM2M endpoint identifier of the device.
      manufacturer:
        type: string
        description: The device manufacturer.
      groupId:
        type: string
        description: The Inventory group ID to attach the device to.
  steps:
  - stepId: createDevice
    description: >-
      Create the Inventory device record with the supplied endpoint and
      manufacturer metadata and a name tag.
    operationId: createDevice
    requestBody:
      contentType: application/json
      payload:
        endpoint: $inputs.endpoint
        manufacturer: $inputs.manufacturer
        tags:
          name: $inputs.deviceName
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      deviceId: $response.body#/device_id
  - stepId: setDeviceGroup
    description: >-
      Add the newly created device to the supplied Inventory group.
    operationId: setDeviceGroup
    parameters:
    - name: device_id
      in: path
      value: $steps.createDevice.outputs.deviceId
    requestBody:
      contentType: application/json
      payload:
        groupId: $inputs.groupId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      groupId: $response.body#/groupId
  - stepId: confirmDevice
    description: >-
      Read the device back to confirm it now reports membership in the target
      group.
    operationId: getDevice
    parameters:
    - name: device_id
      in: path
      value: $steps.createDevice.outputs.deviceId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      finalGroupId: $response.body#/groupId
      online: $response.body#/online
  outputs:
    deviceId: $steps.createDevice.outputs.deviceId
    groupId: $steps.confirmDevice.outputs.finalGroupId

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/soracom-register-device-to-group-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.