View the technical docs for our webhook here:
https://docs.medicare.healthsherpa.com/webhooks/introduction

Push enrollment data to your CRM automatically

Our webhook pushes real-time enrollment data directly to your CRM or system of record at the moment an enrollment is submitted.

No exports, no manual dual entry, no lag.

How it works

When an enrollment is submitted through HealthSherpa Medicare we send a payload to your destination URL with the enrollment data in the payload.

Enrollment submissions from across your agency account and any connected downline agent accounts will trigger a webhook to your endpoint.

Note: Any downline sub-agency accounts are not included, but sub-agencies are each able to set up their own webhook.

Getting started

To set up a webhook, you'll need to:

Create a HealthSherpa agency account (guide). Note: If you're an individual agent, you can still convert to an agency account.
Email medicare-integrations@healthsherpa.com to configure your webhook. You will need to provide:
1. An API key we will use to authenticate with your server (This will be passed as an X-API-Key header)
2. A destination URL on your server, we will send webhooks to this URL
Implement your destination URL to ingest the Submission Payload Schema. Once your webhook is set up, go to your integrations tab and click "Send sample payload" which sends a payload you can test with.

Video tutorials

These walkthroughs show how to connect your HealthSherpa Medicare webhook to a CRM. Before following along, make sure you've completed the Getting Started steps above to activate your webhook.

Setting up with your CRM directly (Salesforce, GoHighLevel, Zoho, etc.)

Use this if your CRM supports inbound webhooks natively – most do, including GoHighLevel (Automations), Salesforce (Flows), and Zoho (Flows).

Setting up with Zapier

Use this if you want to route enrollment data to any app Zapier supports – Trello, Google Sheets, HubSpot, and hundreds more.

Fields included

We include fields from the enrollment and contact records – see the full list here.

A note about agency accounts:

Your agency account and any connected downline agent accounts are included in the scope of this webhook.

Enrollments from downline accounts joined to you as captive agents send all application and contact fields in the payload.
Enrollments from downline accounts joined to you as independent agents receive all application fields and a limited subset of contact fields.
See the Submission payload schema for full field details.

A note about external_id:

If a contact is created directly in the HealthSherpa UI (rather than passed in via API), the webhook will return external_id: null. You can backfill this value using the PATCH endpoint on the Contacts API – see the contact schema docs for details. Once set, all future webhooks for that contact will include the external_id.

Details

Event types
- Currently, one event type is supported: enrollment submission.
Retries
- There are three automatic retries – at 20 seconds, 10 minutes, and 1 hour after the initial delivery, if it fails.

FAQ

What's a webhook?

Our webhook is an automated, real-time notification system that sends data from our platform to your CRM instantly when a enrollment submission event occurs.

What's a destination URL?

A destination URL (also called a callback URL or webhook URL) is a web address your CRM generates that can receive data.

What's an API key?

An API key is a password-like string your CRM generates so we can authenticate when sending data to your endpoint. Not all CRMs require one (e.g., Zapier embeds authentication in the URL itself). If your CRM doesn't provide one, let us know and we'll work with you.

Does this work with my CRM?

The webhook works with any system that can receive an HTTP POST request to a URL. This includes GoHighLevel, Salesforce, Zoho, HubSpot, and most modern CRMs. You can also use Zapier or Make to connect to CRMs that don't have native inbound webhooks. For AgencyBloc specifically, a native integration is coming soon.

Does the webhook distinguish between new enrollments and re-submits?

No. Every enrollment submission fires the same event with the same payload structure regardless of whether it's a new enrollment, rewrite, or replacement.

What should I use to deduplicate or match contacts?

We recommend matching on first name + last name + MBI, or first name + last name + date of birth. The confirmation_number field is guaranteed unique per enrollment. The contact id is a stable UUID for each contact in our system.

Is my client data safe?

HealthSherpa does not sell, market to, or otherwise use your client data. The webhook sends data only to the destination URL you provide. See our privacy policy for details.