POST
/
enrollments
curl --request POST \
  --url https://enrollments.us.stedi.com/2024-09-01/enrollments \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '{
  "transactions": {
    "claimPayment": {
      "enroll": true
    }
  },
  "primaryContact": {
    "firstName": "John",
    "lastName": "Doe",
    "email": "test@example.com",
    "phone": "555-123-34354",
    "streetAddress1": "123 Some Str.",
    "city": "A City",
    "state": "MD",
    "zipCode": "20814"
  },
  "userEmail": "test@example.com",
  "payer": {
    "idOrAlias": "87726"
  },
  "provider": {
    "id": "db6665c5-7b97-4af9-8c68-a00a336c2998"
  },
  "source": "API"
}'
{
  "id": "db6675c5-7bg7-4af9-8c68-a54a336d2911",
  "primaryContact": {
    "firstName": "John",
    "lastName": "Doe",
    "email": "test@example.com",
    "phone": "555-123-34354",
    "streetAddress1": "123 Some Str.",
    "city": "A City",
    "state": "MD",
    "zipCode": "20814"
  },
  "userEmail": "test@example.com",
  "createdAt": "2023-11-07T05:31:56Z",
  "updatedAt": "2023-11-07T05:31:56Z",
  "submittedAt": "2023-11-07T05:31:56Z",
  "transactions": {
    "claimPayment": {
      "enroll": true
    }
  },
  "status": "SUBMITTED",
  "provider": {
    "name": "Test Medical Provider",
    "id": "db6665c5-7b97-4af9-8c68-a00a336c2998"
  },
  "payer": {
    "name": "UnitedHealthcare",
    "stediPayerId": "87726"
  },
  "source": "API"
}

This is a beta endpoint. We may make backwards incompatible changes.

This endpoint allows you to submit a request to enroll a provider for a transaction type with a payer. For example, you might need to enroll a provider with Medicaid for 835 ERAs (claim payments). Submitting enrollment requests through the API is especially useful when you need to submit bulk enrollments for many providers at once, or if you want to embed enrollment capabilities into your own software platform.

Before you can submit an enrollment request, you must add the provider’s details through either the Providers page or the Create Provider endpoint. Then, you must create one enrollment request for each transaction type. For example, you would create three separate requests to enroll a provider for 837P claims (professional), 270 real-time eligibility checks, and 835 ERAs (claim payments).

Once submitted, Stedi handles the entire enrollment process for you, including submitting the enrollment to the payer, following up as needed, and giving clear guidance for any additional steps that might be required.

After you submit an enrollment request, you can review its details and status on the Enrollments page in Stedi. Alternatively, you can retrieve enrollment details programmatically using the Get Enrollment and List Enrollments endpoints.

​
What is transaction enrollment?

All payers require providers to complete an enrollment process before they can start receiving claim remittances (ERAs). Some payers also require enrollment before allowing providers to submit transactions like claims and eligibility checks.

Transaction enrollment involves submitting information about the provider that will send or receive transactions, including the provider’s name, tax ID, NPI, billing address, and contact information.

Visit Transaction enrollment for more details.

You can find out if a payer requires enrollment for a particular transaction type in the Stedi Payer Network.

​
Enrollment status

You can create enrollment requests in DRAFT status first and change the status to SUBMITTED later when you’re ready to submit them to Stedi. Stedi only gets alerted about new enrollment requests once they’re in SUBMITTED status. Once an enrollment is set to SUBMITTED, only Stedi can set or update its status.

Stedi changes the status to PROVISIONING when we begin the enrollment process with the payer.

When an enrollment status is set to LIVE, the provider can start exchanging the enrolled transaction type with the payer.

In rare cases, the enrollment status might be set to REJECTED if the payer denies the enrollment request. Rejections can happen for many reasons, but the most common are that the provider isn’t credentialed with the payer and that there was incorrect data in the enrollment submission. If this happens, Stedi will contact you in Slack to help resolve the issue.

You can cancel an enrollment at any time by contacting Stedi support. Once an enrollment is canceled, Stedi sets its status to CANCELED and stops the enrollment process.

​
Contacts

You must add a contact to an enrollment request. The payer may reach out to this contact with updates or questions about the enrollment. If you’re a provider, this should be your information. If you’re a vendor representing a provider, you can submit your contact information instead of the provider’s information.

Authorizations

​
Authorization
string
header
required

A Stedi API Key for authentication.

Body

application/json

Response

200
application/json
CreateEnrollment 200 response

The response is of type object.