Thryve Webhook Update: Moving to the New v6 Format

Thryve’s notification webhooks are getting a major upgrade. The new v6 data format introduces a cleaner, more standardized, and future-proof structure that enhances integration stability and scalability across all customer applications. This update is more than just a technical fix; it’s part of Thryve's commitment to making health data delivery quicker, more reliable, and easier for developers to build upon in the future. So let’s quickly go through what’s changing, why it matters, and how customers can prepare for the transition to v6.

Why We’re Upgrading

The existing webhook structure has served us well, but was originally designed around earlier integration needs. As our customers’ use cases have grown, from simple notifications to complex, multi-device health monitoring systems, the webhook payload needed more flexibility and clarity.

The v6 format addresses these needs by:

• Standardizing structure: Unified naming conventions and predictable JSON formatting.
• Improving readability: Simplified payloads make debugging and development easier.
• Enhancing version control: Clearer version tagging for long-term compatibility.
• Future-proofing data delivery: Built to handle richer, multi-dimensional data streams such as combined wearable, lab, or survey data.

The update lays the foundation for faster API integration and ensures seamless compatibility with upcoming Thryve features.

What’s Changing with v6

While the core webhook logic remains the same, the payload format and data organization have been restructured for clarity. 

Key improvements include:

• Unified Object Structure: Every webhook now follows a consistent schema with top-level attributes (event_type, timestamp, data, meta).
• Better Contextual Metadata: Each notification includes source identifiers, version numbers, and user context fields for easier correlation.
• Simplified Event Types: Redundant or legacy event categories are consolidated to streamline integration logic.
• Improved Error Handling: Clearer response codes and standardized retry headers for reliable delivery.
• Extended Data Fields: Support for additional biometric and contextual data coming from Thryve’s expanded API ecosystem.

These updates ensure that webhook data is easy to parse and consistent across all endpoints, making integration of Thryve into digital health workflows simpler for our partners.

What Are The Benefits for Developers and Integrators

For development teams, the move to v6 means less overhead and fewer integration pitfalls.

• Simpler Onboarding: The new schema minimizes the need for custom parsing logic.
• Reduced Maintenance: Consistent data structures simplify version upgrades.
• Stronger Validation: Built-in field definitions make it easier to verify payload integrity.
• Future-Ready: Developers can adopt upcoming Thryve features without re-architecting their webhook endpoints.

In short, v6 allows customers to spend less time maintaining integrations and more time using data to create value, from health monitoring dashboards to AI-powered prevention programs.

How To Migrate to V6

Thryve will continue to support existing webhook versions temporarily to ensure a smooth transition. However, all new integrations and future feature releases will be based exclusively on v6.

Migration Guidance:

1. Review the updated v6 webhook documentation in the Thryve Developer Portal.
2. Adjust your payload parsing to the new object hierarchy.
3. Verify error handling, retries, and event subscriptions.
4. Update your configuration to subscribe to v6 events only.

Thryve’s customer success and developer support teams are available to guide you through the migration process step-by-step.

What’s Coming Next

Alongside the v6 webhook upgrade, Thryve is preparing to launch v6 interfaces for epoch daily data — a major step toward even more precise, efficient, and flexible data delivery.

These upcoming interfaces will include enhanced data structures, expanded metric coverage, and improved timestamp accuracy. They’re designed to handle richer health event streams, enabling developers and partners to work with higher-resolution datasets and deeper contextual insights.

This update will be covered in detail in our next release announcement, where we’ll walk through the new features, implementation guidance, and migration options. Stay tuned as the next generation of Thryve’s API ecosystem is just around the corner.

How To Get Started

The v6 webhook documentation is now live. All new customers will onboard directly on v6, while existing integrations are encouraged to migrate as soon as possible..

Book a demo with Thryve to find out more about our solution!