Availity · Arazzo Workflow

Availity Eligibility and Benefits (X12 270/271)

Version 1.0.0

Locate a payer that supports the 270 transaction, submit an X12 270 eligibility request, then retrieve the resulting 271 benefit response.

1 workflow 1 source API 1 provider
View Spec View on GitHub HealthcareClearinghouseHIPAAX12 EDIEligibilityClaimsPrior AuthorizationRevenue Cycle ManagementPayersPrice TransparencyArazzoWorkflows

Provider

availity

Workflows

eligibility-benefits
Find a 270-capable payer, submit the eligibility inquiry, and read the 271 benefit response.
Implements the X12 270/271 eligibility/benefit sequence end to end: payer lookup, 270 inquiry submission, and retrieval of the 271 benefit response.
3 steps inputs: eligibilityRequest outputs: benefits, eligibilityId
1
findPayer
Locate a payer in the Availity directory that supports the X12 270 eligibility transaction.
2
checkEligibility
Submit the X12 270 eligibility inquiry for the member to the selected payer.
3
getEligibility
Retrieve the completed X12 271 benefit response by its Availity transaction id.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Availity Eligibility and Benefits (X12 270/271)
  summary: Locate a payer that supports the 270 transaction, submit an X12 270 eligibility request, then retrieve the resulting 271 benefit response.
  description: >-
    The canonical Availity eligibility flow, modeled on the X12 270/271 health
    care eligibility/benefit inquiry and response transaction set. A payer that
    supports the 270 transaction is located, an eligibility inquiry is submitted
    for the member, and the completed 271 benefit response is read back by its
    Availity transaction id. Every step inlines its request so the flow is
    self-contained.
  version: 1.0.0
  x-realizes-capability-ids:
  - BC-2800.30
  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-2800.30
      capability_name: Eligibility & Benefits Verification
      spec: availity-eligibility-api-openapi.yml
      confidence: 0.9
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: eligibilityApi
  url: ../openapi/availity-eligibility-api-openapi.yml
  type: openapi
workflows:
- workflowId: eligibility-benefits
  summary: Find a 270-capable payer, submit the eligibility inquiry, and read the 271 benefit response.
  description: >-
    Implements the X12 270/271 eligibility/benefit sequence end to end: payer
    lookup, 270 inquiry submission, and retrieval of the 271 benefit response.
  inputs:
    type: object
    required:
    - eligibilityRequest
    properties:
      eligibilityRequest:
        type: object
        description: The X12 270 eligibility inquiry packet (payer, provider, subscriber, and requested service types).
  steps:
  - stepId: findPayer
    description: Locate a payer in the Availity directory that supports the X12 270 eligibility transaction.
    operationId: listPayers
    parameters:
    - name: supportedTransaction
      in: query
      value: "270"
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      payers: $response.body
  - stepId: checkEligibility
    description: Submit the X12 270 eligibility inquiry for the member to the selected payer.
    operationId: checkEligibility
    requestBody:
      contentType: application/json
      payload: $inputs.eligibilityRequest
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      eligibilityId: $response.body#/id
  - stepId: getEligibility
    description: Retrieve the completed X12 271 benefit response by its Availity transaction id.
    operationId: getEligibility
    parameters:
    - name: id
      in: path
      value: $steps.checkEligibility.outputs.eligibilityId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      benefits: $response.body
  outputs:
    eligibilityId: $steps.checkEligibility.outputs.eligibilityId
    benefits: $steps.getEligibility.outputs.benefits

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/availity-eligibility-benefits-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.