generated: '2026-08-15' method: searched source: https://www.stedi.com/docs/healthcare/test-mode docs: - https://www.stedi.com/docs/healthcare/test-mode - https://www.stedi.com/docs/healthcare/api-reference/mock-requests-eligibility-checks - https://www.stedi.com/docs/healthcare/test-claims-workflow - https://www.stedi.com/docs/healthcare/mbi-lookup summary: > Stedi separates test from production by API KEY TYPE and an account-level Test mode toggle, not by a separate host or path — every mock request goes to the same production base URL (https://healthcare.us.stedi.com/2024-04-01/...) with a Test key. Test mode returns canned payer responses only: Stedi publishes a fixed set of mock request bodies and states that "you must use the exact values in the test request. Other birth dates, first names, last names, member IDs, and Social Security Numbers return errors." There is no custom mock data and no payer selection beyond the published fixtures. Mock eligibility checks are free. modes: - name: test selector: Test-type API key + account Test mode toggle key_creation: > Portal > account name in side navigation > API Keys > Generate new API Key, then choose Test as the key type. Stedi's docs suggest naming the key with a `test` prefix. enable: > Production accounts toggle Test mode ON from the account menu at any time. Sandbox accounts are limited to test mode until they upgrade. billing: Mock real-time eligibility checks are free. - name: production selector: Production-type API key with Test mode OFF note: Production API keys inherit the permissions of the account member who created them. hosts: separate_test_host: false note: Test and production share the same base URLs. Only the key type changes. supported_in_test: - Mock real-time eligibility checks (270/271), JSON and Raw X12 - MBI (Medicare Beneficiary Identifier) lookups against the CMS mock payer - Test claims through the API or SFTP (production accounts only) - MCP server (production accounts only; sandbox accounts must upgrade first) - Stedi portal UI exploration not_supported_in_test: - Transaction enrollment - Insurance discovery checks - Coordination of benefits (COB) checks - Submitting claims through the Stedi portal UI - 275 claim attachments - 276/277 real-time claim status - Custom mock data or arbitrary payer selection fixtures: note: > Published verbatim on the eligibility mock-requests reference. Every mock uses provider NPI 1999999984. These are the provider's own documented test values, reproduced as data. provider_npi: '1999999984' by_member_id: - payer: Aetna tradingPartnerServiceId: '60054' subscriber: {firstName: John, lastName: Doe, memberId: AETNA9wcSu} - payer: Anthem Blue Cross Blue Shield of CA tradingPartnerServiceId: '040' subscriber: {firstName: Jane, lastName: Doe, memberId: CGMBCBSCA123} - payer: Blue Cross and Blue Shield of Texas tradingPartnerServiceId: G84980 subscriber: {firstName: John, lastName: Doe, memberId: A2CBCBSTX123} - payer: Cigna tradingPartnerServiceId: '62308' subscriber: {firstName: John, lastName: Doe, memberId: CIGNAJTUxNm} - payer: Oscar Health tradingPartnerServiceId: OSCAR subscriber: {firstName: John, lastName: Doe, memberId: OSCAR123456} - payer: UnitedHealthcare tradingPartnerServiceId: '87726' subscriber: {firstName: John, lastName: Doe, memberId: UHC202649} by_date_of_birth: - payer: Aetna tradingPartnerServiceId: '60054' subscriber: {firstName: Jane, lastName: Doe, dateOfBirth: '20040404'} - payer: Humana tradingPartnerServiceId: '68069' subscriber: {firstName: John, lastName: Doe, dateOfBirth: '19940404'} - payer: Cigna tradingPartnerServiceId: '62308' subscriber: {firstName: Rolando, lastName: Arrojo, dateOfBirth: '19710102'} - payer: Cigna tradingPartnerServiceId: '62308' subscriber: {firstName: Rod, lastName: Beck, dateOfBirth: '19720203'} - payer: Cigna tradingPartnerServiceId: '62308' subscriber: {firstName: David, lastName: Cone, dateOfBirth: '19730304'} - payer: Cigna tradingPartnerServiceId: '62308' subscriber: {firstName: Frank, lastName: Castillo, dateOfBirth: '19750405'} - payer: Cigna tradingPartnerServiceId: '62308' subscriber: {firstName: Casey, lastName: Fossum, dateOfBirth: '19760506'} - payer: Cigna tradingPartnerServiceId: '62308' subscriber: {firstName: Rich, lastName: Garces, dateOfBirth: '19770607'} - payer: Kaiser (KSRCN) tradingPartnerServiceId: KSRCN subscriber: {firstName: Jane, lastName: Doe, dateOfBirth: '20020202'} - payer: CMS (Medicare) tradingPartnerServiceId: CMS subscriber: {firstName: Jane, lastName: Doe, dateOfBirth: '19550505'} - payer: UnitedHealthcare tradingPartnerServiceId: '87726' subscriber: {firstName: Jane, lastName: Doe, dateOfBirth: '19710101'} - payer: '61101' tradingPartnerServiceId: '61101' subscriber: {firstName: Jane, lastName: Doe, dateOfBirth: '19750505'} mbi_lookup: - tradingPartnerServiceId: MBILU subscriber: {lastName: Doe, dateOfBirth: '19550505'} controlNumber: '112233445' note: Medicare Beneficiary Identifier lookup mock. agent_error_fixture: payer: Stedi Agent (mock payer) tradingPartnerServiceId: STEDI subscriber: {firstName: Bernie, lastName: Prohas, memberId: '23051322', dateOfBirth: '20010714'} returns: AAA error 73 (Invalid/Missing Subscriber/Insured Name) purpose: Demonstrates the Stedi Agent error-resolution flow against a deliberate rejection. dental_and_other: - tradingPartnerServiceId: AMTAS00425 subscriber: {firstName: Plaque, lastName: Penguin} - tradingPartnerServiceId: '84103' subscriber: {firstName: Aardvark, lastName: Dent, dateOfBirth: '19701212'} - tradingPartnerServiceId: '62308' subscriber: {firstName: Jaguar, lastName: Dent, dateOfBirth: '19960505'} - tradingPartnerServiceId: '10134' subscriber: {firstName: Elephant, lastName: Dent, dateOfBirth: '19840229'} - tradingPartnerServiceId: '52133' subscriber: {firstName: Beaver, lastName: Dent, dateOfBirth: '19690628'} strictness: exact_match_required: true quote: > "You must use the exact values in the test request. Other birth dates, first names, last names, member IDs, and Social Security Numbers return errors." time_simulation: supported: false note: No test clock or time-travel facility is documented. trigger_tooling: webhooks: supported: true mechanism: > Event destinations can be tested with a `event.ping` validation event, and events can be re-delivered with the RetryEvent operation (POST /events/{eventId}/retry). docs: https://www.stedi.com/docs/healthcare/event-destinations-configure cli: false cli_note: Stedi publishes no CLI with fixture/trigger commands. related: conventions: conventions/stedi-conventions.yml authentication: authentication/stedi-authentication.yml events: asyncapi/stedi-event-destinations-asyncapi.yml