Sign in

Search for payers by name, ID, or alias.

get/payers/search

Query parameters

pageSizeinteger

The maximum number of elements to return in a page. If not specified, the default is 20.

The maximum number of elements to return in a page. If not specified, the default is 20.

pageTokenstring

An opaque token returned by a previous call to this endpoint in the nextPageToken property. You can use it to request the next page of results. If not specified, Stedi returns the first page of results.

An opaque token returned by a previous call to this endpoint in the nextPageToken property. You can use it to request the next page of results. If not specified, Stedi returns the first page of results.

querystring

The query Stedi will use to search the Payer Network database. You can supply a payer's name, ID, or alias. The query is case-insensitive, and fuzzy matching is supported. For example, cig, 62308, and SX071 all return Cigna in the results. If not provided, the other search options are used to conduct the search.

The query Stedi will use to search the Payer Network database. You can supply a payer's name, ID, or alias. The query is case-insensitive, and fuzzy matching is supported. For example, cig, 62308, and SX071 all return Cigna in the results. If not provided, the other search options are used to conduct the search.

eligibilityCheck'SUPPORTED' | 'NOT_SUPPORTED' | 'ENROLLMENT_REQUIRED' | 'EITHER'

Transaction support filter values. When multiple transaction filters are specified, they are combined with AND logic (payers must satisfy all criteria).

Filter for matching payers with the specified 270 eligibility checks support. When combined with other transaction filters, payers must satisfy all specified criteria to be included in results.

claimStatus'SUPPORTED' | 'NOT_SUPPORTED' | 'ENROLLMENT_REQUIRED' | 'EITHER'

Transaction support filter values. When multiple transaction filters are specified, they are combined with AND logic (payers must satisfy all criteria).

Filter for matching payers with the specified 276/277 real-time claim status checks support. When combined with other transaction filters, payers must satisfy all specified criteria to be included in results.

professionalClaimSubmission'SUPPORTED' | 'NOT_SUPPORTED' | 'ENROLLMENT_REQUIRED' | 'EITHER'

Transaction support filter values. When multiple transaction filters are specified, they are combined with AND logic (payers must satisfy all criteria).

Filter for matching payers with the specified 837 professional claims support. When combined with other transaction filters, payers must satisfy all specified criteria to be included in results.

dentalClaimSubmission'SUPPORTED' | 'NOT_SUPPORTED' | 'ENROLLMENT_REQUIRED' | 'EITHER'

Transaction support filter values. When multiple transaction filters are specified, they are combined with AND logic (payers must satisfy all criteria).

Filter for matching payers with the specified 837 dental claims support. When combined with other transaction filters, payers must satisfy all specified criteria to be included in results.

institutionalClaimSubmission'SUPPORTED' | 'NOT_SUPPORTED' | 'ENROLLMENT_REQUIRED' | 'EITHER'

Transaction support filter values. When multiple transaction filters are specified, they are combined with AND logic (payers must satisfy all criteria).

Filter for matching payers with the specified 837 institutional claims support. When combined with other transaction filters, payers must satisfy all specified criteria to be included in results.

claimPayment'SUPPORTED' | 'NOT_SUPPORTED' | 'ENROLLMENT_REQUIRED' | 'EITHER'

Transaction support filter values. When multiple transaction filters are specified, they are combined with AND logic (payers must satisfy all criteria).

Filter for matching payers with the specified 835 Electronic Remittance Advice (ERA) support. When combined with other transaction filters, payers must satisfy all specified criteria to be included in results.

coordinationOfBenefits'SUPPORTED' | 'NOT_SUPPORTED' | 'ENROLLMENT_REQUIRED' | 'EITHER'

Transaction support filter values. When multiple transaction filters are specified, they are combined with AND logic (payers must satisfy all criteria).

Filter for matching payers with the specified coordination of benefits (COB) checks support. When combined with other transaction filters, payers must satisfy all specified criteria to be included in results.

unsolicitedClaimAttachment'SUPPORTED' | 'NOT_SUPPORTED' | 'ENROLLMENT_REQUIRED' | 'EITHER'

Transaction support filter values. When multiple transaction filters are specified, they are combined with AND logic (payers must satisfy all criteria).

Filter for matching payers with the specified unsolicited 275 claim attachments support. When combined with other transaction filters, payers must satisfy all specified criteria to be included in results.

coverageTypesCoverageType[]

Filter for matching payers that support transactions for all of the specified coverage types. For example, setting this array to ["medical", "dental"] returns only payers who provide both medical and dental coverage.

The results also exclude payers without coverage type classifications in Stedi's database.

Filter for matching payers that support transactions for all of the specified coverage types. For example, setting this array to ["medical", "dental"] returns only payers who provide both medical and dental coverage.

The results also exclude payers without coverage type classifications in Stedi's database.

operatingStatesOperatingStateCode[]

Filter for matching payers that operate in all of the specified states, territories, or NATIONAL. For example, setting this array to ["CA", "OR"] returns only payers that operate in both California and Oregon. Setting it to ["NATIONAL"] returns payers that operate in all 50 U.S. states. To find payers that also operate in territories, you must include those territory codes explicitly, for example ["NATIONAL", "PR"].

The results also exclude payers without operating state classifications in Stedi's database.

Filter for matching payers that operate in all of the specified states, territories, or NATIONAL. For example, setting this array to ["CA", "OR"] returns only payers that operate in both California and Oregon. Setting it to ["NATIONAL"] returns payers that operate in all 50 U.S. states. To find payers that also operate in territories, you must include those territory codes explicitly, for example ["NATIONAL", "PR"].

The results also exclude payers without operating state classifications in Stedi's database.

programsProgram[]

Filter for matching payers that participate in any of the specified insurance programs. For example, setting this array to ["MEDICARE", "TRICARE"] returns payers that participate in either Medicare or TRICARE.

The results also exclude payers without program classifications in Stedi's database.

Filter for matching payers that participate in any of the specified insurance programs. For example, setting this array to ["MEDICARE", "TRICARE"] returns payers that participate in either Medicare or TRICARE.

The results also exclude payers without program classifications in Stedi's database.

Response

SearchPayers 200 response

nextPageTokenstring

Token that you can supply in subsequent requests to retrieve the next page of results. If not returned, there are no more results.

Changes

Changed in 10 of the 23 revisions of this API.121324

  • 45a2088b99ae64See the full diff
    • ▲

      removed the required property items/items/payer/transactionSupport/claimPaymentAdviceWithElectronicFundsTransfer from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property items/items/payer/transactionSupport/electronicFundsTransfer from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property stats/transactionSupport/claimPaymentAdviceWithElectronicFundsTransfer from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property stats/transactionSupport/electronicFundsTransfer from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property stats/transactionSupportCounts/claimPaymentAdviceWithElectronicFundsTransfer from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property stats/transactionSupportCounts/electronicFundsTransfer from the response with the 200 status

      response-required-property-removed

    • ●

      deleted the query request parameter claimPaymentAdviceWithElectronicFundsTransfer

      request-parameter-removed

    • ●

      deleted the query request parameter electronicFundsTransfer

      request-parameter-removed

    • ●

      removed the optional property items/items/payer/enrollment/transactionEnrollmentProcesses/claimPaymentAdviceWithElectronicFundsTransfer from the response with the 200 status

      response-optional-property-removed

    • ●

      removed the optional property items/items/payer/enrollment/transactionEnrollmentProcesses/electronicFundsTransfer from the response with the 200 status

      response-optional-property-removed

    This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • 15409ffbbb1f10See the full diff
    • ○

      added the new optional query request parameter claimPaymentAdviceWithElectronicFundsTransfer

      new-optional-request-parameter

    • ○

      added the new optional query request parameter electronicFundsTransfer

      new-optional-request-parameter

    • ○

      added the optional property items/items/payer/enrollment/transactionEnrollmentProcesses/claimPaymentAdviceWithElectronicFundsTransfer to the response with the 200 status

      response-optional-property-added

    • ○

      added the optional property items/items/payer/enrollment/transactionEnrollmentProcesses/electronicFundsTransfer to the response with the 200 status

      response-optional-property-added

    • ○

      added the required property items/items/payer/transactionSupport/claimPaymentAdviceWithElectronicFundsTransfer to the response with the 200 status

      response-required-property-added

    • ○

      added the required property items/items/payer/transactionSupport/electronicFundsTransfer to the response with the 200 status

      response-required-property-added

    • ○

      added the required property stats/transactionSupport/claimPaymentAdviceWithElectronicFundsTransfer to the response with the 200 status

      response-required-property-added

    • ○

      added the required property stats/transactionSupport/electronicFundsTransfer to the response with the 200 status

      response-required-property-added

    • ○

      added the required property stats/transactionSupportCounts/claimPaymentAdviceWithElectronicFundsTransfer to the response with the 200 status

      response-required-property-added

    • ○

      added the required property stats/transactionSupportCounts/electronicFundsTransfer to the response with the 200 status

      response-required-property-added

  • 1dcc06bebd7c1See the full diff
    • ○

      added the optional property items/items/payer/parentPayerGroupName to the response with the 200 status

      response-optional-property-added

  • 2e49f8d2681611See the full diff
    • ●

      added the new FM enum value to the items/items/payer/operatingStates/items/ response property for the response status 200

      response-property-enum-value-added

    • ○

      added the enum value FM to the property items/ of the query request parameter operatingStates

      request-parameter-property-enum-value-added

  • 8d8ddbb544f42See the full diff
    • ○

      added the new optional query request parameter programs

      new-optional-request-parameter

    • ○

      added the required property items/items/payer/programs to the response with the 200 status

      response-required-property-added

  • f204c80764e88See the full diff
    • ●

      added the new OVER_4_WEEKS enum value to the items/items/payer/enrollment/transactionEnrollmentProcesses/claimPayment/timeframe response property for the response status 200

      response-property-enum-value-added

    • ●

      added the new OVER_4_WEEKS enum value to the items/items/payer/enrollment/transactionEnrollmentProcesses/claimStatusInquiry/timeframe response property for the response status 200

      response-property-enum-value-added

    • ●

      added the new OVER_4_WEEKS enum value to the items/items/payer/enrollment/transactionEnrollmentProcesses/coordinationOfBenefits/timeframe response property for the response status 200

      response-property-enum-value-added

    • ●

      added the new OVER_4_WEEKS enum value to the items/items/payer/enrollment/transactionEnrollmentProcesses/dentalClaim/timeframe response property for the response status 200

      response-property-enum-value-added

    • ●

      added the new OVER_4_WEEKS enum value to the items/items/payer/enrollment/transactionEnrollmentProcesses/eligibilityInquiry/timeframe response property for the response status 200

      response-property-enum-value-added

    • ●

      added the new OVER_4_WEEKS enum value to the items/items/payer/enrollment/transactionEnrollmentProcesses/institutionalClaim/timeframe response property for the response status 200

      response-property-enum-value-added

    • ●

      added the new OVER_4_WEEKS enum value to the items/items/payer/enrollment/transactionEnrollmentProcesses/professionalClaim/timeframe response property for the response status 200

      response-property-enum-value-added

    • ●

      added the new OVER_4_WEEKS enum value to the items/items/payer/enrollment/transactionEnrollmentProcesses/unsolicitedClaimAttachment/timeframe response property for the response status 200

      response-property-enum-value-added

  • a9f77441413a1See the full diff
    • ○

      added the optional property items/items/payer/conciseName to the response with the 200 status

      response-optional-property-added

  • a38f3b6eb3f98See the full diff
    • ○

      added the optional property items/items/payer/enrollment/transactionEnrollmentProcesses/claimPayment/requestedEffectiveDate to the response with the 200 status

      response-optional-property-added

    • ○

      added the optional property items/items/payer/enrollment/transactionEnrollmentProcesses/claimStatusInquiry/requestedEffectiveDate to the response with the 200 status

      response-optional-property-added

    • ○

      added the optional property items/items/payer/enrollment/transactionEnrollmentProcesses/coordinationOfBenefits/requestedEffectiveDate to the response with the 200 status

      response-optional-property-added

    • ○

      added the optional property items/items/payer/enrollment/transactionEnrollmentProcesses/dentalClaim/requestedEffectiveDate to the response with the 200 status

      response-optional-property-added

    • ○

      added the optional property items/items/payer/enrollment/transactionEnrollmentProcesses/eligibilityInquiry/requestedEffectiveDate to the response with the 200 status

      response-optional-property-added

    • ○

      added the optional property items/items/payer/enrollment/transactionEnrollmentProcesses/institutionalClaim/requestedEffectiveDate to the response with the 200 status

      response-optional-property-added

    • ○

      added the optional property items/items/payer/enrollment/transactionEnrollmentProcesses/professionalClaim/requestedEffectiveDate to the response with the 200 status

      response-optional-property-added

    • ○

      added the optional property items/items/payer/enrollment/transactionEnrollmentProcesses/unsolicitedClaimAttachment/requestedEffectiveDate to the response with the 200 status

      response-optional-property-added

  • 4e17a39792b26See the full diff
    • ▲

      the code response property's minLength was decreased from 1 to 0 for the response status 401

      response-property-min-length-decreased

    • ▲

      the code response property's minLength was decreased from 1 to 0 for the response status 404

      response-property-min-length-decreased

    • ▲

      the code response property's minLength was decreased from 1 to 0 for the response status 500

      response-property-min-length-decreased

    • ▲

      the message response property's minLength was decreased from 1 to 0 for the response status 401

      response-property-min-length-decreased

    • ▲

      the message response property's minLength was decreased from 1 to 0 for the response status 404

      response-property-min-length-decreased

    • ▲

      the message response property's minLength was decreased from 1 to 0 for the response status 500

      response-property-min-length-decreased

  • dd2d5eea5d5f1See the full diff
    • ○

      added the optional property items/items/payer/enrollment/transactionEnrollmentProcesses/claimPayment/supportedAggregationPreferences to the response with the 200 status

      response-optional-property-added