---
title: "Can enrollment instructions be emailed to a practice through an outside portal?"
slug: "can-enrollment-instructions-be-emailed-to-a-practice-through-an-outside-portal"
updated: 2026-02-04T19:45:30Z
published: 2026-02-04T19:45:30Z
canonical: "docs.claim.md/can-enrollment-instructions-be-emailed-to-a-practice-through-an-outside-portal"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.claim.md/llms.txt
> Use this file to discover all available pages before exploring further.

# Can enrollment instructions be emailed to a practice through an outside portal?

Not directly. While Claim.MD does provide an API-driven enrollment workflow, the enrollment URLs generated by the API are **intentionally short-lived** and are **not designed to be emailed or stored for later use**.

This distinction is especially important as Claim.MD introduces multi-TIN support and enrollment activity increases through external applications.

### Why enrollment links cannot be emailed

The Enrollment Request API returns a **one-time authorization URL** that expires very quickly—typically within **about 30 seconds** of being generated. Because of this short lifespan:

- The link **cannot be sent via email** for later use
- The link **cannot be generated in advance** and reused minutes later
- Attempting to open an expired link will result in an **“authorization unavailable”** message

This behavior is by design and is intended to protect enrollment security and ensure the link is only used in an active, user-initiated session.

### Intended enrollment workflow

The enrollment request API is designed for **real-time, on-demand use** within your application or portal. The expected flow is:

1. A user initiates enrollment for a specific payer within your application (for example, by clicking an **Enroll** button).
2. At that moment, your backend calls the Claim.MD Enrollment Request API:

```

TextTextPOST /services/enroll/
```
3. Claim.MD returns a one-time-use enrollment URL (for 1500 or ERA enrollment).
4. Your application **immediately redirects the user’s browser** to that URL.

Because the link expires so quickly, it must be generated and consumed as part of the same interaction. Delaying use—even by a few minutes—will cause the link to fail.

### What this means for external portals

Although enrollment links cannot be emailed like form-fillable documents, external portals can still support customer-managed enrollments by:

- Triggering enrollment links **on demand**
- Redirecting users immediately into Claim.MD-hosted enrollment instructions or forms
- Eliminating most back-and-forth by guiding users through the process in real time

This approach allows practices to complete enrollments themselves without needing direct Claim.MD access, while still maintaining strict security controls.

### API reference

Full documentation for the Enrollment Request API is available here: [https://api.claim.md/#/paths/~1services~1enroll~1/post](https://api.claim.md/#/paths/~1services~1enroll~1/post)