MobileAPI.dev · Arazzo Workflow

MobileAPI Autocomplete and Resolve Device

Version 1.0.0

Turn a partial typeahead string into a confirmed device record.

1 workflow 1 source API 1 provider
View Spec View on GitHub Data APIDeveloper ToolsDevice SpecificationsMobile DataPhone SpecsREST APISoftware-as-a-ServiceArazzoWorkflows

Provider

mobileapi-dev

Workflows

autocomplete-and-resolve-device
Autocomplete a partial query, then search and read the resolved device.
Requests autocomplete suggestions for a partial query string, uses the top suggestion's name to search the catalog for the best match, and reads the full device record for that match.
3 steps inputs: apiKey, q, suggestionLimit outputs: deviceId, deviceName, manufacturerName
1
autocomplete
Request typeahead suggestions for the partial query string, returning a simplified list of candidate device names.
2
findDevice
Search the catalog for the top autocomplete suggestion, limiting to the single best match to resolve a concrete device id.
3
readDevice
Read the full device record for the resolved id, returning the complete specification block.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: MobileAPI Autocomplete and Resolve Device
  summary: Turn a partial typeahead string into a confirmed device record.
  description: >-
    Models the typeahead-to-detail journey. The workflow asks the autocomplete
    endpoint for suggestions matching a partial query string, then takes the
    top suggestion name, searches for it to resolve a concrete device id, and
    reads the full device record. 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: devicesApi
  url: ../openapi/mobileapi-dev-devices-api-openapi.yml
  type: openapi
workflows:
- workflowId: autocomplete-and-resolve-device
  summary: Autocomplete a partial query, then search and read the resolved device.
  description: >-
    Requests autocomplete suggestions for a partial query string, uses the top
    suggestion's name to search the catalog for the best match, and reads the
    full device record for that match.
  inputs:
    type: object
    required:
    - apiKey
    - q
    properties:
      apiKey:
        type: string
        description: MobileAPI key, sent in the Authorization header as 'Token <apiKey>'.
      q:
        type: string
        description: Partial query string for autocomplete (minimum 5 characters).
      suggestionLimit:
        type: integer
        description: Maximum number of autocomplete suggestions to return (default 10, max 30).
  steps:
  - stepId: autocomplete
    description: >-
      Request typeahead suggestions for the partial query string, returning a
      simplified list of candidate device names.
    operationId: devices_autocomplete
    parameters:
    - name: Authorization
      in: header
      value: "Token $inputs.apiKey"
    - name: q
      in: query
      value: $inputs.q
    - name: limit
      in: query
      value: $inputs.suggestionLimit
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      topSuggestionName: $response.body#/0/name
  - stepId: findDevice
    description: >-
      Search the catalog for the top autocomplete suggestion, limiting to the
      single best match to resolve a concrete device id.
    operationId: devices_search
    parameters:
    - name: Authorization
      in: header
      value: "Token $inputs.apiKey"
    - name: name
      in: query
      value: $steps.autocomplete.outputs.topSuggestionName
    - name: limit
      in: query
      value: 1
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      deviceId: $response.body#/id
      deviceName: $response.body#/name
  - stepId: readDevice
    description: >-
      Read the full device record for the resolved id, returning the complete
      specification block.
    operationId: devices_read
    parameters:
    - name: id
      in: path
      value: $steps.findDevice.outputs.deviceId
    - name: Authorization
      in: header
      value: "Token $inputs.apiKey"
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      manufacturerName: $response.body#/manufacturer_name
      deviceType: $response.body#/device_type
  outputs:
    deviceId: $steps.findDevice.outputs.deviceId
    deviceName: $steps.findDevice.outputs.deviceName
    manufacturerName: $steps.readDevice.outputs.manufacturerName

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/mobileapi-dev-autocomplete-resolve-device-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.