Product Updates

Integrate HealthTasks with Power BI via our REST API

Pull HealthTasks clinical education data into Power BI with Power Query and your institution API key - no certified connector required.

HealthTasks

Jul 15, 2026 — 2 min read

When we introduced the HealthTasks REST API, the goal was to connect clinical education data to the systems your institution already runs.

For many programs, that includes Power BI.

Integrate HealthTasks with Power BI via our REST API

HealthTasks publishes a documented OpenAPI REST API. Power BI Desktop can call that API with Power Query, pass your institution API key in a request header, and shape the JSON into tables for dashboards leadership already uses.

HealthTasks stays the system of record for clinical education. Power BI stays where institutional reporting already lives. This is an OpenAPI-backed integration path, not a Microsoft certified connector or AppSource listing.

The same pattern underpins our Salesforce integration: public OpenAPI on our side, native ingestion tools on theirs.

How analysts connect it

1. Create an institution API key

In HealthTasks, go to Settings → REST API and generate a key. Prefer a read-scoped key for reporting. Do not paste production keys into shared workbooks or public docs.

Base URL:

https://app.healthtasks.ai/api/v1

HealthTasks accepts the key as x-healthtasks-api-key or as Authorization: Bearer.

2. Pull a resource in Power Query

In Power BI Desktop, open Get data → Blank query, then open the Advanced Editor. A minimal pattern looks like this:

let
  apiKey = "YOUR_API_KEY",
  url = "https://app.healthtasks.ai/api/v1/students",
  source = Json.Document(
    Web.Contents(
      url,
      [
        Headers = [
          #"x-healthtasks-api-key" = apiKey
        ]
      ]
    )
  )
in
  source

Replace students with site_placements, compliance_statuses, clinical_logs, or another list endpoint from the API docs. Convert the record or list to a table, expand nested fields, and keep only the columns your model needs.

List endpoints support limit (default 500, max 500) and cursor for pagination. Use updated_since when you want incremental pulls.

Store the API key in a Power BI parameter or a secured credential pattern for your tenant. Do not hard-code production secrets in shared PBIX files that travel by email.

3. Build the model and refresh

Relate student, placement, and compliance tables the way your program reports today. Refresh in Desktop whenever you need a current pull.

For Power BI Service scheduled refresh, plan for your tenant’s rules around Web.Contents and gateways. Some orgs require an on-premises data gateway or an approved custom connector pattern when custom headers are involved. Start in Desktop, then have IT validate the service refresh path before you promise a fully hands-off dashboard.

Why this beats spreadsheet exports

Manual CSV drops drift the moment a placement or clearance changes. A REST pull into Power Query keeps clinical education metrics on the same refresh cadence as the rest of your institutional reporting - without waiting on a vendor-built Power BI connector.