Stedi · Arazzo Workflow

Stedi Provider Enrollment for X12 835 ERA/EFT

Version 1.0.0

Create a provider, open an enrollment, upload the signed agreement, and read the enrollment status for X12 835 ERA/EFT transactions.

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

Provider

stedi

Workflows

provider-enrollment
Create a provider, open an enrollment, upload the agreement, and read the X12 835 ERA/EFT enrollment status.
Registers a provider, opens a payer enrollment for X12 835 ERA/EFT, uploads the signed enrollment document, and reads the resulting enrollment status.
4 steps inputs: document, enrollment, provider outputs: enrollment, enrollmentId, providerId
1
createProvider
Register the provider record that the payer enrollment will be opened against.
2
createEnrollment
Open the enrollment with the payer for X12 835 ERA/EFT transactions.
3
uploadDocument
Upload the signed enrollment agreement document for the open enrollment.
4
getEnrollment
Read the enrollment back to confirm its status after the document upload.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Stedi Provider Enrollment for X12 835 ERA/EFT
  summary: Create a provider, open an enrollment, upload the signed agreement, and read the enrollment status for X12 835 ERA/EFT transactions.
  description: >-
    The canonical Stedi provider enrollment flow, which registers a provider with a
    payer for X12 835 electronic remittance advice and EFT delivery in the healthcare
    revenue cycle, following the same trading-partner enrollment pattern as X12 834.
    A provider record is created, an enrollment is opened against a payer, the signed
    enrollment document is uploaded, and the enrollment is read back for its status.
    Every step inlines its request so the flow is self-contained.
  version: 1.0.0
  x-realizes-capability-ids:
  - BC-2890.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-2890.50
      capability_name: Provider Enrolment Management
      spec: stedi-providers-api-openapi.yml
      confidence: 0.78
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: enrollmentsApi
  url: ../openapi/stedi-enrollments-api-openapi.yml
  type: openapi
- name: providersApi
  url: ../openapi/stedi-providers-api-openapi.yml
  type: openapi
workflows:
- workflowId: provider-enrollment
  summary: Create a provider, open an enrollment, upload the agreement, and read the X12 835 ERA/EFT enrollment status.
  description: >-
    Registers a provider, opens a payer enrollment for X12 835 ERA/EFT, uploads the
    signed enrollment document, and reads the resulting enrollment status.
  inputs:
    type: object
    required:
    - provider
    - enrollment
    - document
    properties:
      provider:
        type: object
        description: Provider record (name, NPI, tax id, contact) to register with Stedi enrollment.
      enrollment:
        type: object
        description: Enrollment request (payer, provider, transaction types such as 835 ERA/EFT) to open against the payer.
      document:
        type: object
        description: Enrollment document upload packet (file name, content type) for the signed payer agreement.
  steps:
  - stepId: createProvider
    description: Register the provider record that the payer enrollment will be opened against.
    operationId: CreateProvider
    requestBody:
      contentType: application/json
      payload: $inputs.provider
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      providerId: $response.body#/id
  - stepId: createEnrollment
    description: Open the enrollment with the payer for X12 835 ERA/EFT transactions.
    operationId: CreateEnrollment
    requestBody:
      contentType: application/json
      payload: $inputs.enrollment
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      enrollmentId: $response.body#/id
  - stepId: uploadDocument
    description: Upload the signed enrollment agreement document for the open enrollment.
    operationId: CreateEnrollmentDocumentUpload
    parameters:
    - name: enrollmentId
      in: path
      value: $steps.createEnrollment.outputs.enrollmentId
    requestBody:
      contentType: application/json
      payload: $inputs.document
    successCriteria:
    - condition: $statusCode == 200
  - stepId: getEnrollment
    description: Read the enrollment back to confirm its status after the document upload.
    operationId: GetEnrollment
    parameters:
    - name: enrollmentId
      in: path
      value: $steps.createEnrollment.outputs.enrollmentId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      enrollment: $response.body
  outputs:
    providerId: $steps.createProvider.outputs.providerId
    enrollmentId: $steps.createEnrollment.outputs.enrollmentId
    enrollment: $steps.getEnrollment.outputs.enrollment

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-provider-enrollment-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.