Stedi · Arazzo Workflow

Stedi X12 276/277 Claim Status Inquiry

Version 1.0.0

Resolve a claim-status-capable payer, run an X12 276 inquiry, and convert the X12 277 status report.

1 workflow 1 source API 1 provider
View Spec View on GitHub EDIElectronic Data InterchangeHealthcareClearinghouseX12ClaimsEligibilityHIPAARevenue Cycle ManagementB2B IntegrationArazzoWorkflows

Provider

stedi

Workflows

claim-status-inquiry
Find a claim-status-capable payer, run the X12 276 inquiry, and convert the X12 277 report.
Resolves the payer in the Stedi network with 276/277 claim-status support, then submits the X12 276 inquiry and converts the X12 277 status report.
3 steps inputs: payerQuery, statusRequest outputs: payerStediId, report, transactionId
1
findPayer
SearchPayers
Resolve the payer in the Stedi network and confirm it supports X12 276/277 real-time claim status.
2
inquireStatus
ClaimStatus
Submit the X12 276 claim-status inquiry to the payer through the Stedi network.
3
getReport
ConvertReport277
Convert the resulting transaction into a human-readable X12 277 claim-status report.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Stedi X12 276/277 Claim Status Inquiry
  summary: Resolve a claim-status-capable payer, run an X12 276 inquiry, and convert the X12 277 status report.
  description: >-
    The canonical Stedi claim-status flow, encoding the X12 276/277 transaction set
    for the healthcare revenue cycle. A payer is resolved from the Stedi network
    with its claim-status support confirmed, an X12 276 inquiry is submitted, and the
    resulting transaction is converted into a human-readable X12 277 status report.
    Every step inlines its request so the flow is self-contained.
  version: 1.0.0
sourceDescriptions:
- name: stediHealthcare
  url: ../openapi/stedi-healthcare-openapi.yml
  type: openapi
workflows:
- workflowId: claim-status-inquiry
  summary: Find a claim-status-capable payer, run the X12 276 inquiry, and convert the X12 277 report.
  description: >-
    Resolves the payer in the Stedi network with 276/277 claim-status support, then
    submits the X12 276 inquiry and converts the X12 277 status report.
  inputs:
    type: object
    required:
    - payerQuery
    - statusRequest
    properties:
      payerQuery:
        type: string
        description: Free-text search to resolve the payer (name or payer id) in the Stedi payer network.
      statusRequest:
        type: object
        description: X12 276 claim-status inquiry packet (controlNumber, tradingPartnerServiceId, provider, subscriber, claim reference).
  steps:
  - stepId: findPayer
    description: Resolve the payer in the Stedi network and confirm it supports X12 276/277 real-time claim status.
    operationId: SearchPayers
    parameters:
    - name: query
      in: query
      value: $inputs.payerQuery
    - name: claimStatus
      in: query
      value: true
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      payerStediId: $response.body#/payers/0/stediId
  - stepId: inquireStatus
    description: Submit the X12 276 claim-status inquiry to the payer through the Stedi network.
    operationId: ClaimStatus
    requestBody:
      contentType: application/json
      payload: $inputs.statusRequest
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      transactionId: $response.body#/transactionId
  - stepId: getReport
    description: Convert the resulting transaction into a human-readable X12 277 claim-status report.
    operationId: ConvertReport277
    parameters:
    - name: transactionId
      in: path
      value: $steps.inquireStatus.outputs.transactionId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      report: $response.body
  outputs:
    payerStediId: $steps.findPayer.outputs.payerStediId
    transactionId: $steps.inquireStatus.outputs.transactionId
    report: $steps.getReport.outputs.report

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/stedi-claim-status-inquiry-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 email required.

A second provider on the same verified email joins the account you already have.