Stedi Enrollments API
The Enrollments API from Stedi — 4 operation(s) for enrollments.
OpenAPI Specification
openapi: 3.0.3
info:
contact:
email: healthcare@stedi.com
license:
name: Proprietary
url: https://stedi.com
title: Stedi Healthcare Claims Claim acknowledgments Enrollments API
version: '2025-03-07'
servers:
- description: Production
url: https://claims.us.stedi.com/2025-03-07
security:
- httpApiKeyAuth: []
tags:
- name: Enrollments
paths:
/enrollments:
get:
description: Lists transaction enrollment records with optional filtering and pagination.
operationId: ListEnrollments
parameters:
- description: The maximum number of elements to return in a page. If not specified, the default is 100.
in: query
name: pageSize
schema:
description: The maximum number of elements to return in a page. If not specified, the default is 100.
maximum: 500
minimum: 1
type: number
- description: The `nextPageToken` value from a previous response. You can use this to get the next page of results. If not set, Stedi returns the first page of results.
in: query
name: pageToken
schema:
description: The `nextPageToken` value from a previous response. You can use this to get the next page of results. If not set, Stedi returns the first page of results.
maxLength: 1024
minLength: 1
type: string
- description: 'Filter for enrollments with properties matching a query string.
You can provide all or part of a provider name, NPI, or tax ID. You can also provide all or part of a payer''s [Stedi payer ID](https://www.stedi.com/docs/healthcare/supported-payers#stedi-payer-id) - primary payer IDs and aliases aren''t supported. The search is case-insensitive and supports fuzzy matching.
For example, providing `?filter=OS` returns enrollments with `provider.name` containing `os` or `OS` (such as `Joseph`) and Stedi payer IDs containing `OS`, such as `OSBLI` for OptumHealth Salt Lake County.'
in: query
name: filter
schema:
description: 'Filter for enrollments with properties matching a query string.
You can provide all or part of a provider name, NPI, or tax ID. You can also provide all or part of a payer''s [Stedi payer ID](https://www.stedi.com/docs/healthcare/supported-payers#stedi-payer-id) - primary payer IDs and aliases aren''t supported. The search is case-insensitive and supports fuzzy matching.
For example, providing `?filter=OS` returns enrollments with `provider.name` containing `os` or `OS` (such as `Joseph`) and Stedi payer IDs containing `OS`, such as `OSBLI` for OptumHealth Salt Lake County.'
type: string
- description: 'Filter for enrollments with specific statuses.
You can include this parameter multiple times to filter for multiple statuses. For example, `?status=LIVE&status=REJECTED` returns enrollments that are in either `LIVE` or `REJECTED` status.'
explode: true
in: query
name: status
schema:
description: 'Filter for enrollments with specific statuses.
You can include this parameter multiple times to filter for multiple statuses. For example, `?status=LIVE&status=REJECTED` returns enrollments that are in either `LIVE` or `REJECTED` status.'
items:
$ref: '#/components/schemas/EnrollmentStatus'
type: array
style: form
- description: 'Filter for enrollments associated with specific provider NPIs.
You can include this parameter multiple times to filter for multiple NPIs. For example, `?providerNpis=1234567890&providerNpis=0987654321` returns enrollments associated with either of the specified NPIs.'
explode: true
in: query
name: providerNpis
schema:
description: 'Filter for enrollments associated with specific provider NPIs.
You can include this parameter multiple times to filter for multiple NPIs. For example, `?providerNpis=1234567890&providerNpis=0987654321` returns enrollments associated with either of the specified NPIs.'
items:
type: string
type: array
style: form
- description: 'Filter for enrollments associated with specific provider tax IDs.
You can include this parameter multiple times to filter for multiple tax IDs. For example, `?providerTaxIds=123456789&providerTaxIds=987654321` returns enrollments associated with either of the specified tax IDs.'
explode: true
in: query
name: providerTaxIds
schema:
description: 'Filter for enrollments associated with specific provider tax IDs.
You can include this parameter multiple times to filter for multiple tax IDs. For example, `?providerTaxIds=123456789&providerTaxIds=987654321` returns enrollments associated with either of the specified tax IDs.'
items:
type: string
type: array
style: form
- description: 'Filter for enrollments associated with specific provider names.
This search is case-insensitive but doesn''t support fuzzy matching. The name you provide must match the provider''s name exactly, including spaces, but capitalization is ignored.
You can include this parameter multiple times to filter for multiple names. For example, `?providerNames=John%20Doe&providerNames=Jane%20Doe` returns enrollments associated with either John Doe or Jane Doe.'
explode: true
in: query
name: providerNames
schema:
description: 'Filter for enrollments associated with specific provider names.
This search is case-insensitive but doesn''t support fuzzy matching. The name you provide must match the provider''s name exactly, including spaces, but capitalization is ignored.
You can include this parameter multiple times to filter for multiple names. For example, `?providerNames=John%20Doe&providerNames=Jane%20Doe` returns enrollments associated with either John Doe or Jane Doe.'
items:
type: string
type: array
style: form
- description: 'Filter for enrollments associated with specific provider IDs.
The provider ID is a UUID Stedi assigns to each provider record upon creation, allowing you to differentiate between provider records that share the same NPI. It''s returned in the `id` property of the [Create Provider](/healthcare/api-reference/post-enrollment-create-provider#response.id) and [Retrieve Provider](/healthcare/api-reference/get-enrollment-provider#response.id) responses.
You can include this parameter multiple times to filter for multiple providers. For example, `?providerIds=10334e76-f073-4b5d-8984-81d8e5107857&providerIds=10234e76-f067-4b5d-8984-81d8e5107123` returns enrollments associated with either of the specified providers.'
explode: true
in: query
name: providerIds
schema:
description: 'Filter for enrollments associated with specific provider IDs.
The provider ID is a UUID Stedi assigns to each provider record upon creation, allowing you to differentiate between provider records that share the same NPI. It''s returned in the `id` property of the [Create Provider](/healthcare/api-reference/post-enrollment-create-provider#response.id) and [Retrieve Provider](/healthcare/api-reference/get-enrollment-provider#response.id) responses.
You can include this parameter multiple times to filter for multiple providers. For example, `?providerIds=10334e76-f073-4b5d-8984-81d8e5107857&providerIds=10234e76-f067-4b5d-8984-81d8e5107123` returns enrollments associated with either of the specified providers.'
items:
type: string
type: array
style: form
- description: "Filter for enrollments associated with specific [Stedi payer IDs](https://www.stedi.com/docs/healthcare/supported-payers#stedi-payer-id).\n\nThis parameter only supports Stedi payer IDs, not primary payer IDs or aliases. It also doesn't support fuzzy matching. The payer ID you provide must match the Stedi payer ID exactly, including capitalization. You must include leading `0` characters - for example, use `00540` for SISCO, not `540`. \n\nYou can include this parameter multiple times to filter for multiple payer IDs. For example, `?payerIds=HGJLR&payerIds=EWDCI` returns enrollments associated with either of the specified payer IDs."
explode: true
in: query
name: payerIds
schema:
description: "Filter for enrollments associated with specific [Stedi payer IDs](https://www.stedi.com/docs/healthcare/supported-payers#stedi-payer-id).\n\nThis parameter only supports Stedi payer IDs, not primary payer IDs or aliases. It also doesn't support fuzzy matching. The payer ID you provide must match the Stedi payer ID exactly, including capitalization. You must include leading `0` characters - for example, use `00540` for SISCO, not `540`. \n\nYou can include this parameter multiple times to filter for multiple payer IDs. For example, `?payerIds=HGJLR&payerIds=EWDCI` returns enrollments associated with either of the specified payer IDs."
items:
type: string
type: array
style: form
- description: 'Filter for enrollments submitted through specific sources, such as the API or UI.
You can include this parameter multiple times to filter for multiple sources. For example, `?sources=API&sources=UI` returns enrollments submitted through either of the specified sources.'
explode: true
in: query
name: sources
schema:
description: 'Filter for enrollments submitted through specific sources, such as the API or UI.
You can include this parameter multiple times to filter for multiple sources. For example, `?sources=API&sources=UI` returns enrollments submitted through either of the specified sources.'
items:
$ref: '#/components/schemas/EnrollmentSource'
type: array
style: form
- description: 'Filter for enrollments for specific transaction types.
You can include this parameter multiple times to filter for multiple types. For example, `?transactions=eligibilityCheck&transactions=claimStatus` returns enrollments for both 270/271 eligibility checks and 276/277 real-time claim status.'
explode: true
in: query
name: transactions
schema:
description: 'Filter for enrollments for specific transaction types.
You can include this parameter multiple times to filter for multiple types. For example, `?transactions=eligibilityCheck&transactions=claimStatus` returns enrollments for both 270/271 eligibility checks and 276/277 real-time claim status.'
items:
$ref: '#/components/schemas/TransactionType'
type: array
style: form
- description: 'Filter for enrollments created from a specific date.
For example, if you set this to `2025-01-01T00:00:00Z`, Stedi returns enrollments with a `createdAt` timestamp on or after this date.'
in: query
name: createdFrom
schema:
description: 'Filter for enrollments created from a specific date.
For example, if you set this to `2025-01-01T00:00:00Z`, Stedi returns enrollments with a `createdAt` timestamp on or after this date.'
format: date-time
type: string
- description: 'Filter for enrollments created before a specific date. The time must be later than `createdFrom`, if present.
For example, if you set this to `2025-01-01T00:00:00Z`, Stedi only returns enrollments with a `createdAt` timestamp before this date.'
in: query
name: createdTo
schema:
description: 'Filter for enrollments created before a specific date. The time must be later than `createdFrom`, if present.
For example, if you set this to `2025-01-01T00:00:00Z`, Stedi only returns enrollments with a `createdAt` timestamp before this date.'
format: date-time
type: string
- description: 'Filter for enrollments whose status was last updated from a specific date.
For example, if you set this to `2025-01-01T00:00:00Z`, Stedi returns enrollments with a `statusLastUpdatedAt` timestamp on or after this date.'
in: query
name: statusUpdatedFrom
schema:
description: 'Filter for enrollments whose status was last updated from a specific date.
For example, if you set this to `2025-01-01T00:00:00Z`, Stedi returns enrollments with a `statusLastUpdatedAt` timestamp on or after this date.'
format: date-time
type: string
- description: 'Filter for enrollments whose status was last updated before a specific date. The time must be later than `statusUpdatedFrom`, if present.
For example, if you set this to `2025-01-01T00:00:00Z`, Stedi only returns enrollments with a `statusLastUpdatedAt` before this date.'
in: query
name: statusUpdatedTo
schema:
description: 'Filter for enrollments whose status was last updated before a specific date. The time must be later than `statusUpdatedFrom`, if present.
For example, if you set this to `2025-01-01T00:00:00Z`, Stedi only returns enrollments with a `statusLastUpdatedAt` before this date.'
format: date-time
type: string
- description: The import ID associated with an enrollment through a CSV bulk import. This ID is only available for enrollments created through the CSV import process.
in: query
name: importId
schema:
description: The import ID associated with an enrollment through a CSV bulk import. This ID is only available for enrollments created through the CSV import process.
type: string
- description: 'Filter for enrollments with a requested effective date on or after this date, in YYYYMMDD format.
For example, `?requestedEffectiveDateFrom=20260101` returns enrollments with a `requestedEffectiveDate` of `20260101` or later.'
in: query
name: requestedEffectiveDateFrom
schema:
description: 'Filter for enrollments with a requested effective date on or after this date, in YYYYMMDD format.
For example, `?requestedEffectiveDateFrom=20260101` returns enrollments with a `requestedEffectiveDate` of `20260101` or later.'
maxLength: 8
minLength: 8
pattern: ^\d{8}$
type: string
- description: 'Filter for enrollments with a requested effective date on or before this date, in YYYYMMDD format. The date must be the same as or later than `requestedEffectiveDateFrom`, if present.
For example, `?requestedEffectiveDateTo=20261231` returns enrollments with a `requestedEffectiveDate` of `20261231` or earlier.'
in: query
name: requestedEffectiveDateTo
schema:
description: 'Filter for enrollments with a requested effective date on or before this date, in YYYYMMDD format. The date must be the same as or later than `requestedEffectiveDateFrom`, if present.
For example, `?requestedEffectiveDateTo=20261231` returns enrollments with a `requestedEffectiveDate` of `20261231` or earlier.'
maxLength: 8
minLength: 8
pattern: ^\d{8}$
type: string
- description: 'Filter for enrollments with a `lastEraReceivedAt` timestamp on or after this value. Only enrollments with an ERA are included.
You can use this filter with `lastEraReceivedTo` to define a date range. For example, setting this to `2025-01-01T00:00:00Z` returns enrollments with a `lastEraReceivedAt` on or after that date.'
in: query
name: lastEraReceivedFrom
schema:
description: 'Filter for enrollments with a `lastEraReceivedAt` timestamp on or after this value. Only enrollments with an ERA are included.
You can use this filter with `lastEraReceivedTo` to define a date range. For example, setting this to `2025-01-01T00:00:00Z` returns enrollments with a `lastEraReceivedAt` on or after that date.'
format: date-time
type: string
- description: 'Filter for enrollments with a `lastEraReceivedAt` timestamp on or before this value. Only enrollments with an ERA are included. This value must be later than `lastEraReceivedFrom`, if present.
For example, setting this to `2025-01-01T00:00:00Z` returns enrollments with a `lastEraReceivedAt` on or before that date.'
in: query
name: lastEraReceivedTo
schema:
description: 'Filter for enrollments with a `lastEraReceivedAt` timestamp on or before this value. Only enrollments with an ERA are included. This value must be later than `lastEraReceivedFrom`, if present.
For example, setting this to `2025-01-01T00:00:00Z` returns enrollments with a `lastEraReceivedAt` on or before that date.'
format: date-time
type: string
- description: 'Filter for enrollments associated with specific submitter emails. This is the `userEmail` property in [Create Enrollment](https://www.stedi.com/docs/healthcare/api-reference/post-enrollment-create-enrollment) requests, or the **Stedi contact person** in the portal.
This search is case-insensitive but doesn''t support fuzzy matching. The email you provide must match the submitter''s email exactly, but capitalization is ignored.
You can include this parameter multiple times to filter for multiple submitter emails. For example, `?userEmails=alice%40example.com&userEmails=bob%40example.com` returns enrollments submitted by either `alice@example.com` or `bob@example.com`.'
explode: true
in: query
name: userEmails
schema:
description: 'Filter for enrollments associated with specific submitter emails. This is the `userEmail` property in [Create Enrollment](https://www.stedi.com/docs/healthcare/api-reference/post-enrollment-create-enrollment) requests, or the **Stedi contact person** in the portal.
This search is case-insensitive but doesn''t support fuzzy matching. The email you provide must match the submitter''s email exactly, but capitalization is ignored.
You can include this parameter multiple times to filter for multiple submitter emails. For example, `?userEmails=alice%40example.com&userEmails=bob%40example.com` returns enrollments submitted by either `alice@example.com` or `bob@example.com`.'
items:
description: A valid email address following standard email format.
minLength: 5
pattern: ^[a-zA-Z0-9.!#$%&'*+/=?^_`{|}~-]+@[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?(?:\.[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?)*$
type: string
type: array
style: form
- description: "Sort the results by one or more properties. By default, Stedi sorts results by the `createdAt` property in descending order.\n\nSupply a query string with each property appended using `&`. Each property must be provided in a `property:direction` format, where `property` is the name of the property to sort by and `direction` is the sort direction, either `asc` (ascending) or `desc` (descending).\n - When you don't include `id`, Stedi automatically adds it as the final sort criterion to ensure deterministic results.\n - When you provide multiple properties, Stedi sorts by their order in the query string. For example, if you provide `?sortBy=updatedAt:desc&sortBy=id:asc`, Stedi sorts first by `updatedAt` in descending order. If multiple records share the same `updatedAt` date, Stedi then sorts those records by `id` in ascending order.\n\n**Supported properties:** `updatedAt`, `statusLastUpdatedAt`, `id`, `requestedEffectiveDate`, `lastEraReceivedAt`\n\nExamples:\n - Sort by `updatedAt` in descending order: `?sortBy=updatedAt:desc`\n - Sort by `statusLastUpdatedAt` in ascending order: `?sortBy=statusLastUpdatedAt:asc`\n - Sort by `updatedAt` and then by `id`: `?sortBy=updatedAt:desc&sortBy=id:asc`"
explode: true
in: query
name: sortBy
schema:
description: "Sort the results by one or more properties. By default, Stedi sorts results by the `createdAt` property in descending order.\n\nSupply a query string with each property appended using `&`. Each property must be provided in a `property:direction` format, where `property` is the name of the property to sort by and `direction` is the sort direction, either `asc` (ascending) or `desc` (descending).\n - When you don't include `id`, Stedi automatically adds it as the final sort criterion to ensure deterministic results.\n - When you provide multiple properties, Stedi sorts by their order in the query string. For example, if you provide `?sortBy=updatedAt:desc&sortBy=id:asc`, Stedi sorts first by `updatedAt` in descending order. If multiple records share the same `updatedAt` date, Stedi then sorts those records by `id` in ascending order.\n\n**Supported properties:** `updatedAt`, `statusLastUpdatedAt`, `id`, `requestedEffectiveDate`, `lastEraReceivedAt`\n\nExamples:\n - Sort by `updatedAt` in descending order: `?sortBy=updatedAt:desc`\n - Sort by `statusLastUpdatedAt` in ascending order: `?sortBy=statusLastUpdatedAt:asc`\n - Sort by `updatedAt` and then by `id`: `?sortBy=updatedAt:desc&sortBy=id:asc`"
items:
pattern: ^\w+:(asc|desc)$
type: string
type: array
style: form
responses:
'200':
content:
application/json:
examples:
ListEnrollments_example1:
description: ''
summary: List Enrollments
value:
items:
- aggregationPreference:
taxId: '123456789'
createdAt: '2025-04-01T12:00:00Z'
documents:
- createdAt: '2025-04-01T12:00:00Z'
enrollmentId: db6675c5-7bg7-4af9-8c68-a54a336d2911
id: dc6665a5-7b97-4agh-8c74-a00a336c2989
name: pdf-agreement.pdf
status: UPLOADED
updatedAt: '2025-04-02T12:00:00Z'
history:
- changedAt: '2025-04-15T09:00:00Z'
changedBy: user@example.com
newStatus: DRAFT
type: STATUS_CHANGE
- changedAt: '2025-04-15T09:05:00Z'
changedBy: user@example.com
newStatus: STEDI_ACTION_REQUIRED
previousStatus: DRAFT
type: STATUS_CHANGE
- changedAt: '2025-04-20T14:30:00Z'
changedBy: system
newStatus: PROVIDER_ACTION_REQUIRED
previousStatus: STEDI_ACTION_REQUIRED
type: STATUS_CHANGE
- changedAt: '2025-05-02T12:00:00Z'
changedBy: system
newStatus: PROVISIONING
previousStatus: PROVIDER_ACTION_REQUIRED
type: STATUS_CHANGE
- changedAt: '2025-05-10T15:30:00Z'
changedBy: system
newStatus: LIVE
previousStatus: PROVISIONING
type: STATUS_CHANGE
id: db6675c5-7bg7-4af9-8c68-a54a336d2911
lastEraReceivedAt: '2025-05-02T12:00:00Z'
payer:
name: UnitedHealthcare
stediPayerId: KMQTZ
submittedPayerIdOrAlias: '87726'
provider:
id: db6665c5-7b97-4af9-8c68-a00a336c2998
name: Test Medical Provider
npi: '1234567890'
taxId: '123456789'
taxIdType: EIN
requestedEffectiveDate: '20250415'
source: API
status: LIVE
statusLastUpdatedAt: '2025-05-01T12:00:00Z'
tasks:
- definition:
followInstructions:
instructions: 'Please follow these instructions: <URL>.'
id: ac6665a5-7b97-4agh-8c74-a00a336c2989
isComplete: true
rank: 0
responsibleParty: PROVIDER
transactions:
claimPayment:
enroll: true
updatedAt: '2025-05-01T12:00:00Z'
- createdAt: '2025-04-20T08:15:00Z'
documents:
- createdAt: '2026-11-08T12:00:00Z'
enrollmentId: db6675c5-7bg7-4af9-8c68-a54a336d2911
id: dc6665a5-7b97-4agh-8c74-a00a336c2989
name: pdf-agreement.pdf
status: UPLOADED
updatedAt: '2026-11-08T12:05:00Z'
history:
- changedAt: '2026-11-07T05:31:56Z'
changedBy: user@example.com
newStatus: DRAFT
type: STATUS_CHANGE
- changedAt: '2026-11-07T05:31:56Z'
changedBy: user@example.com
newStatus: STEDI_ACTION_REQUIRED
previousStatus: DRAFT
type: STATUS_CHANGE
- changedAt: '2026-11-07T06:15:22Z'
changedBy: system
newStatus: PROVIDER_ACTION_REQUIRED
previousStatus: STEDI_ACTION_REQUIRED
type: STATUS_CHANGE
- changedAt: '2026-11-08T06:15:22Z'
changedBy: system
newStatus: STEDI_ACTION_REQUIRED
previousStatus: PROVIDER_ACTION_REQUIRED
type: STATUS_CHANGE
- changedAt: '2026-11-10T06:15:22Z'
changedBy: system
newStatus: PROVIDER_ACTION_REQUIRED
previousStatus: STEDI_ACTION_REQUIRED
type: STATUS_CHANGE
id: e9a8b7c6-d5f4-3e2d-1c0b-a9876543210f
payer:
name: Aetna
stediPayerId: AETNA
submittedPayerIdOrAlias: '60054'
provider:
id: a1b2c3d4-e5f6-7890-abcd-ef1234567890
name: Test Medical Provider
npi: '9876543210'
taxId: '987654321'
taxIdType: EIN
reason: Waiting for provider action
requestedEffectiveDate: '20250801'
source: API
status: PROVIDER_ACTION_REQUIRED
statusLastUpdatedAt: '2025-04-22T14:45:00Z'
submittedAt: '2025-04-20T08:20:00Z'
tasks:
- definition:
followInstructions:
instructions: Log in to your Authority's portal and request clearinghouse access for Stedi.
id: f8e7d6c5-b4a3-9281-7654-321098765432
isComplete: false
rank: 1
responsibleParty: PROVIDER
- completedAt: '2026-11-08T06:14:22Z'
definition:
provideFilledPdf:
instructions: Please download the PDF, fill it out, and upload the completed version to this enrollment request.
id: 019ce833-b234-75f1-9599-0f14ba643709
isComplete: true
rank: 0
responseData:
pdfUpload:
documentId: dc6665a5-7b97-4agh-8c74-a00a336c2989
fileName: pdf-agreement.pdf
responsibleParty: PROVIDER
transactions:
eligibilityCheck:
enroll: true
updatedAt: '2025-04-25T10:30:00Z'
nextPageToken: 945ff6de213d3ef481d028065d4c12fb996a166a3a90ef98564318decfae50ce4b36d74b7e9d9bafa6e1d169
totalCount: 42
schema:
$ref: '#/components/schemas/ListEnrollmentsResponseContent'
description: ListEnrollments 200 response
'400':
content:
application/json:
schema:
$ref: '#/components/schemas/ValidationExceptionResponseContent'
description: ValidationException 400 response
'401':
content:
application/json:
schema:
$ref: '#/components/schemas/UnauthorizedExceptionResponseContent'
description: UnauthorizedException 401 response
'403':
content:
application/json:
schema:
$ref: '#/components/schemas/AccessDeniedExceptionResponseContent'
description: AccessDeniedException 403 response
'429':
content:
application/json:
schema:
$ref: '#/components/schemas/QuotaExceededExceptionResponseContent'
description: QuotaExceededException 429 response
'500':
content:
application/json:
schema:
$ref: '#/components/schemas/InternalFailureExceptionResponseContent'
description: InternalFailureException 500 response
'503':
content:
application/json:
schema:
$ref: '#/components/schemas/ServiceUnavailableExceptionResponseContent'
description: ServiceUnavailableException 503 response
'504':
content:
application/json:
schema:
$ref: '#/components/schemas/GatewayTimeoutExceptionResponseContent'
description: GatewayTimeoutException 504 response
tags:
- Enrollments
post:
description: Creates a new transaction enrollment request. Transaction enrollment registers a provider to exchange specific transaction types with a payer.
operationId: CreateEnrollment
requestBody:
content:
application/json:
examples:
CreateEnrollment_example1:
description: ''
summary: Create Enrollment
value:
aggregationPreference:
taxId: '123456789'
payer:
idOrAlias: '87726'
primaryContact:
city: A City
email: test@example.com
firstName: John
lastName: Doe
phone: '5551234567'
state: MD
streetAddress1: 123 Some Str.
zipCode: '20814'
provider:
id: db6665c5-7b97-4af9-8c68-a00a336c2998
requestedEffectiveDate: '20240301'
status: STEDI_ACTION_REQUIRED
transactions:
claimPayment:
enroll: true
userEmail: test@example.com
schema:
$ref: '#/components/schemas/CreateEnrollmentRequestContent'
required: true
responses:
'200':
content:
application/json:
examples:
CreateEnrollment_example1:
description: ''
summary: Create Enrollment
value:
aggregationPreference:
taxId: '123456789'
createdAt: '2023-11-07T05:31:56Z'
# --- truncated at 32 KB (141 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/stedi/refs/heads/main/openapi/stedi-enrollments-api-openapi.yml