Welcome to Recuro Health! Here you'll find comprehensive information for integrating with the Platform and our API endpoints. We've tried to make this documentation user-friendly and example-filled, but if you have any questions, please head to our discussion board for further assistance.

Recuro Health's APIs power its virtual care platform. Behind these APIs is a sophisticated infrastructure that coordinates clinical data, provider and patient communication, billing and claims, eligibility, real-time reporting, and much more.

API Keys and Access

To gain access to the Recuro Health Platform API, please contact your Recuro Health account manager. You will be provided a SubscriptionKey, ClientId, and ClientSecret.

API Protocols

The Recuro Health API uses the GET, POST, PUT, and occasionally DELETE protocols to communicate and HTTP response codes to indicate status and errors. All responses come in standard JSON. The Recuro Health API is served over HTTPS TLS v1.2+ to ensure data privacy; HTTPS with TLS versions below 1.2 are not supported.

API Endpoints

Resource	EndPoint
Authentication	https://platform.wellviasolutions.com/auth/v1
Clinical	https://platform.wellviasolutions.com/clinical/v1
Communication	https://platform.wellviasolutions.com/communication/v1
Event	https://platform.wellviasolutions.com/event/v1
Organization	https://platform.wellviasolutions.com/organization/v1
Payment	https://platform.wellviasolutions.com/payment/v1
Reporting	https://platform.wellviasolutions.com/reporting/v1
Questionnaire	https://platform.wellviasolutions.com/qna/v1
User	https://platform.wellviasolutions.com/user/v1

Breaking Changes

We strive to avoid making any breaking changes to our API, but we do make changes over time that may result in changes to the data that you pull from Recuro Health.

We consider the following changes to be backwards compatible:

Adding new API endpoints
Adding new options parameters to existing endpoints
Adding new data elements to existing response schemas
Adding new error and event types
Changing the length or content of any API identifier

API Release Stages

Most new features and other significant changes follow a formal release process:

Private Beta

This is the earliest stage of availability of a new product. Only clients that have requested and been approved access to this stage of the release process will have access to these changes.

Public Beta

Following private beta, we flag changes as public beta, which allows any authorized client access to these changes. Changes can still occur in this phase, but are usually minor.

General Availability

Changes are available to any authorized client and are considered stable and will follow our standard Breaking Changes policy.