Turn your HealthSherpa book of business into an API

What you can build on HealthSherpa

• Get documents due

  Build this

  Reads the Documents due tab: every connected client with document follow-ups, their status and the earliest deadline.

  Takes

  Status (optional), deadline before (optional)

  Returns

  Client, outstanding docs, status, earliest deadline, last synced at

• Get a client's follow-ups and notices

  Build this

  Opens one client's record on the Details tab and reads the Follow-ups section and Marketplace notices.

  Takes

  Client name

  Returns

  Follow-up, status, deadline, Marketplace notices

• Upload a follow-up document

  Build this

  Opens a client's follow-up, selects Verify and uploads the document you give for the Marketplace to review.

  Takes

  Client name, follow-up, document file

  Returns

  Client, follow-up, status, uploaded at

Automate HealthSherpa with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

• Documents due with a deadline in the next 14 days

  Build this

  Starts

  Every weekday at 8:00

  Step 1

  Get documents due from the Documents due tab.

  Step 2

  Keep the clients whose earliest deadline is within 14 days and whose status starts with Open.

  Step 3

  Email you the list, soonest deadline first.

• Follow-ups that changed status, posted to your CRM

  Build this

  Starts

  Every day at 9:00

  Step 1

  Get documents due, then for each client get the follow-ups and Marketplace notices.

  Step 2

  Keep the follow-ups whose status changed since the last run.

  Step 3

  Post each one with client, follow-up, status, deadline and the newest notice to your CRM webhook.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get documents due” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "healthsherpa.com/get_documents_due",
    "input": {
      "status": "Open, insufficient document"
    }
  }'

{
  "status": "completed",
  "data": {
    "clients": [
      {
        "client": "Jordan Acme",
        "outstanding_docs": 2,
        "status": "Open, insufficient document",
        "earliest_deadline": "2026-12-03",
        "last_synced_at": "2026-11-12T05:14:00-05:00"
      },
      {
        "client": "Riley Northwind",
        "outstanding_docs": 1,
        "status": "Open, insufficient document",
        "earliest_deadline": "2026-12-19",
        "last_synced_at": "2026-11-12T05:14:00-05:00"
      }
    ],
    "count": 2
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

HealthSherpa’s own options

HealthSherpa's Agency Connect APIs send client data in, build prefilled quote links, return plan data and APTC estimates, and export CSV files. Access is approved case by case for agencies and platforms, and the documentation does not list submitting applications. Agents have the Exports page, and HealthSherpa One is its integration platform for agents.

Read on November 12, 2026: Agency Connect documentation, The HealthSherpa export report, FFM account integration with HealthSherpa.

Signing in to HealthSherpa

HealthSherpa asks for your email and password, then a code by text message or from an authenticator app at each login: CMS has required it for agents since August 13, 2025. With Fous you sign in once through HealthSherpa's own sign-in with your own account. The login is sealed with AES-256, never returned by the API or written to logs, and code and AI agents never see it.

Worth knowing

Documents due refreshes once a day

The Documents due tab updates every 24 hours and needs Enhanced Direct Enrollment access. Its Last synced at column shows how fresh each row is, so a morning check reads the day's list.

DMI and SVI clocks run differently

A client has 90 to 95 days to resolve a DMI, counted from the application submission date, not the effective date. An SVI has 30 days from plan selection.

Marketplace data needs the FFM integration

Without an active FFM integration an agent cannot search the Marketplace, submit applications or view clients. Since August 4, 2026, CMS asks you to reintegrate after 30 minutes of inactivity.

Export links last about an hour

Exports from the Exports page arrive as an emailed link that expires about one hour after the email. Agency administrators can turn exports off for their direct downline agents.

More in Insurance

• Allianz Maklerportal
• Aviva Broker
• AXA Connect
• PPL
• Navigate
• Covered California Enroller Portal
• HealthCare.gov for agents and brokers
• HealthEquity employer portal
• Optum Financial employer portal
• WEX Benefits employer portal
• NIPR
• Aflac Business Services
• National General agent portal
• Travelers for Agents
• Nationwide Agent Center
• The Hartford EBC
• Citizens PolicyCenter and myAgency

Other industries: Authorized Paid Representative Portal, CARM Client Portal, Schwab Advisor Center, INTTRA, RMIS, IMDS.