Corsano

Corsano is a comprehensive health monitoring platform that provides continuous vital signs monitoring through wearable technology, enabling healthcare providers and individuals to track health metrics, detect anomalies, and maintain proactive health management.

Power end-to-end data operations for your Corsano API with Nexla. Our bi-directional Corsano connector is purpose-built for Corsano, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Corsano or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Corsano workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Corsano credential, you need to obtain an API key from your Corsano account. The API key is required to authenticate with the Corsano API.

To obtain your API key, you need to have a Corsano account with API access enabled. Once you have access to your account, you can generate an API key from your account settings. The API key is used for API token-based authentication for the Corsano API. The API key is sent as a query parameter (token) in API requests to authenticate all API calls to the Corsano API. For detailed information about API key setup and authentication, refer to the Corsano API documentation.

Authenticate

Credentials required

API token based authentication for Corsano API.

Field	Required	Secret	Description
API Server URL	Yes	No	Enter the URL for the API Server URL you wish to connect to.
API URL for Validating Credential	Yes	No	Enter a URL that can be used for validating the credential during credential creation. Leave the default setting for bypassing credential validation during this step and instead enforcing it during source configuration.
API Key	Yes	Yes	Your Corsano API Key for sending authenticated requests to Corsano API.

Create a credential in Nexla

1. To create a new Corsano credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Corsano

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter the URL for the API Server URL you wish to connect to in the API Server URL field. This should be the base URL for your Corsano API instance. The default value is https://api.integration.corsano.com if not specified.

   The API Server URL should be the base URL for your Corsano API instance. The default value is https://api.integration.corsano.com if not specified. The API Server URL is used to construct the full endpoint URLs for API requests.

4. Enter a URL that can be used for validating the credential during credential creation in the API URL for Validating Credential field. You can leave the default setting (https://developer.corsano.com) for bypassing credential validation during this step and instead enforcing it during source configuration.

   The API URL for Validating Credential is used to test the credential during credential creation. You can leave the default setting (https://developer.corsano.com) for bypassing credential validation during this step and instead enforcing it during source configuration. This allows you to create the credential and validate it later when configuring the data source.

5. Enter your Corsano API key in the API Key field. This is the API key you obtained from your Corsano account settings. The API key is sent as a query parameter (token) in API requests to authenticate all API calls to the Corsano API.

   Keep your API key secure and do not share it publicly. The API key provides access to your Corsano account and should be treated as sensitive information. The API key is sent as a query parameter (token) in API requests to authenticate all API calls to the Corsano API. For detailed information about obtaining and managing API keys, see the Corsano API documentation.

6. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Corsano connector tile, then select the credential that will be used to connect to the Corsano instance, and click Next; or, create a new Corsano credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Corsano endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Get User Summaries

This endpoint fetches user summaries for users in a group. Use this endpoint when you need to access user summary data, health metrics, or summary information for users in a specific group from your Corsano account.

• Enter the Group ID for fetching summaries in the Group ID field. This is the unique identifier of the group for which you want to fetch user summaries.

• Enter the starting date for getting data in the From Date field. This must be in yyyy-MM-dd format (e.g., 2021-09-24). You can use Nexla macros like {now} for the current time or {now-2} for two days ago. The default value is {now-2} if not specified.

• Enter the end date for getting data in the To Date field. This must be in yyyy-MM-dd format (e.g., 2021-09-25). You can use Nexla macros like {now} for the current time or {now-1} for one day ago. The default value is {now-1} if not specified.

• This endpoint uses a three-step process to fetch user summaries:
• Step 1: Fetches the list of patients in the specified group using GET requests to {api_url}/v1/groups/{group_id}/patients?token={api_key}. The response data is extracted from the root-level array ($[*]), with each patient record processed individually.
• Step 2: For each patient from Step 1, fetches the patient tokens using GET requests to {api_url}/v1/patients/{uuid}/tokens?token={api_key} where {uuid} is the patient UUID from Step 1. The response data is extracted from the root-level object ($), and the health_token is extracted for use in Step 3.
• Step 3: For each patient from Step 1, fetches the user summaries using GET requests to https://api.health.cloud.corsano.com/user-summaries?date_from={'{date_from}'}&date_to={'{date_to}'}&include_slots=1&uuid={'{uuid}'} where {uuid} is the patient UUID from Step 1, {date_from} is the From Date, and {date_to} is the To Date. The request includes the Authorization: Bearer {health_token} header where {health_token} is the health token from Step 2. The response data is extracted from the data array in the API response ($.data[*]), with each summary record processed individually.
• The endpoint does not use pagination and returns all user summaries for the specified group and date range in a single request per patient.

This endpoint uses a three-step chained API call process. First, it fetches the list of patients in the specified group. Then, for each patient, it fetches the patient tokens to obtain the health token. Finally, for each patient, it uses the health token to fetch the user summaries for the specified date range. The endpoint uses static URLs (iteration.type: static.url) and does not require pagination. The response data path for Step 3 is $.data[*], which extracts all items from the data array in the API response. For detailed information about fetching user summaries, see the Corsano API documentation.

Get Raw Metrics

This endpoint fetches raw metrics of different categories for patients in a group. Use this endpoint when you need to access raw health metrics, activity data, heart rate data, temperature data, or sleep data for patients in a specific group from your Corsano account.

• Enter the Group ID for fetching metrics in the Group ID field. This is the unique identifier of the group for which you want to fetch raw metrics.

• Select the metric type you want to retrieve from the Metric Type dropdown menu. Available options are:

  • raw_activities: For fetching raw activity metrics (default)
  • raw_rr_intervals: For fetching raw RR interval metrics
  • raw_heart_rates: For fetching raw heart rate metrics
  • raw_temperatures: For fetching raw temperature metrics
  • raw_sleeps: For fetching raw sleep metrics

  The default value is raw_activities if not specified.

• Enter the starting date for getting data in the From Date field. This must be in yyyy-MM-dd format (e.g., 2021-09-24). You can use Nexla macros like {now} for the current time or {now-2} for two days ago. The default value is {now-2} if not specified.

• Enter the end date for getting data in the To Date field. This must be in yyyy-MM-dd format (e.g., 2021-09-25). You can use Nexla macros like {now} for the current time or {now-1} for one day ago. The default value is {now-1} if not specified.

• This endpoint uses a three-step process to fetch raw metrics:
• Step 1: Fetches the list of patients in the specified group using GET requests to {api_url}/v1/groups/{group_id}/patients?token={api_key}. The response data is extracted from the root-level array ($[*]), with each patient record processed individually.
• Step 2: For each patient from Step 1, fetches the patient tokens using GET requests to {api_url}/v1/patients/{uuid}/tokens?token={api_key} where {uuid} is the patient UUID from Step 1. The response data is extracted from the root-level object ($), and the health_token is extracted for use in Step 3.
• Step 3: For each patient from Step 1, fetches the raw metrics using GET requests to https://api.health.cloud.corsano.com/raw-metrics?only_metrics[]={'{metric_type}'}&date_from={'{date_from}'}&date_to={'{date_to}'} where {uuid} is the patient UUID from Step 1, {metric_type} is the Metric Type you select, {date_from} is the From Date, and {date_to} is the To Date. The request includes the Authorization: Bearer {health_token} header where {health_token} is the health token from Step 2. The response data is extracted from the metric type array in the API response ($.${'{metric_type}'}[*]), with each metric record processed individually.
• The endpoint does not use pagination and returns all raw metrics for the specified group, metric type, and date range in a single request per patient.

This endpoint uses a three-step chained API call process. First, it fetches the list of patients in the specified group. Then, for each patient, it fetches the patient tokens to obtain the health token. Finally, for each patient, it uses the health token to fetch the raw metrics for the specified metric type and date range. The endpoint uses static URLs (iteration.type: static.url) and does not require pagination. The response data path for Step 3 is $.${'{metric_type}'}[*], which extracts all items from the metric type array in the API response. For detailed information about fetching raw metrics, see the Corsano API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Corsano data sources can also be manually configured to ingest data from any valid Corsano API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Corsano API endpoints typically follow the pattern {api_url}/v1/{endpoint_path}?token={api_key}; remember to include the token query parameter with your API key. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Corsano API responses may use different structures like data arrays ($.data[*]) or root-level arrays ($[*]) depending on the endpoint. Use the Test button to verify that your JSON path correctly extracts the desired data from the API response.

Once all configuration steps have been completed, click the Save button to save your data source configuration. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.