Power BI integration

Datpaq data, live in Power BI.

Pull ready-to-model API data into Power BI with Power Query. Scheduled refresh, no middleware, no ETL to babysit.

How Datpaq works with Power BI

Datpaq connects to Microsoft Power BI through Power Query's Web connector. Every Datpaq API returns clean JSON over HTTPS and authenticates with one API key, so you can load calendar tables, exchange rates, geocoded addresses, and economic data straight into your semantic model, then keep it fresh with scheduled refresh.

If you've ever pasted last week's rates into a spreadsheet just so a report would refresh, this one's for you.

Datpaq
Microsoft Power BI
Power BI

Setup

Two ways in

Point and click if you live in reports. Write M if you want parameterized, refresh-safe queries. Both take about five minutes.

For analysts: copy and paste

  1. Copy
    Open any API in your Datpaq dashboard, pick Power BI / Power Query from the code menu, and copy the script. Your key is already filled in.
  2. Paste
    In Power BI Desktop, select Home > Get data > Blank query, open the Advanced Editor, paste, and select Done. Choose Anonymous if asked.
  3. Shape
    Drill into data, convert the list to a table, expand the columns, then Close & Apply.
Sharing the report? Use the M route so your key lives in Power BI's credential store instead of the URL.

For developers: Power Query M

  1. Open
    Select Home > Get data > Blank query, then open the Advanced Editor.
  2. Paste
    Paste a Web.Contents query with the static base URL https://datpaq.com/api/v1, the endpoint in RelativePath, and its parameters in Query.
  3. Authenticate
    When prompted, choose Web API and paste your Datpaq key. Publish, then schedule refresh in the Power BI service.
powerquery
1let2    Year = Text.From(Date.Year(DateTime.LocalNow())),3    // Keep the base URL static; pass the endpoint through RelativePath and Query4    // so the Power BI service can refresh this query on a schedule.5    Response = Json.Document(6        Web.Contents(7            "https://datpaq.com/api/v1",8            [9                RelativePath = "calendar/range",10                Query = [11                    start_date = Year & "-01-01",12                    end_date = Year & "-12-31",13                    include_holidays = "true",14                    country_code = "US"15                ],16                // Power BI asks for your key once (Web API credential).17                ApiKeyName = "api_key"18            ]19        )20    ),21    Days = Table.FromRecords(Response[data][days], null, MissingField.UseNull)22in23    Days
The current year of business days and public holidays from the Calendar API, ready to mark as a date table.

Built for the Power BI service, not just Desktop.

The details that decide whether a report still works on Monday morning. More on keys and encryption on our security page.

Scheduled refresh that actually refreshes

A static base URL with RelativePath and Query lets the Power BI service recognize the data source. Datpaq is a public cloud endpoint, so the Web connector needs no gateway.

Keys stay out of your queries

ApiKeyName stores your Datpaq key in Power BI's credential manager, not in the M code or the .pbix you share. Rotate keys any time from the dashboard.

Usage you can predict

Each Datpaq query makes one request per refresh, counted against your plan's flat monthly ceiling. No surprise overage bills.

Encrypted end to end

Every request travels over HTTPS with TLS, and every call is authenticated against your key and plan.

The Datpaq connector for Power BI Desktop

We're packaging a connector so you can pick Datpaq straight from Get data. Until it ships, everything above works today with Power BI's built-in Web connector.

Coming soon
Get notified

FAQ

Power BI questions

Answers for analysts and developers connecting Datpaq to Power BI.

Can I connect Datpaq to Power BI?

Yes. Power BI connects to any Datpaq API through Power Query's Web connector. Copy a ready-made Power Query script from your Datpaq dashboard into the Advanced Editor, or write your own Web.Contents query. Both work in Power BI Desktop today and refresh in the Power BI service.

Do I need to know Power Query M?

No. Analysts can copy a ready-made Power Query script, key included, from the Datpaq dashboard and paste it into a blank query. The M route is there for developers who want parameterized, refresh-safe queries and keys kept in Power BI's credential store.

Will scheduled refresh work in the Power BI service?

Yes, as long as the base URL passed to Web.Contents is a static string and the endpoint and parameters go through the RelativePath and Query options. URLs assembled from text at runtime count as dynamic data sources, which the Power BI service can't refresh.

How do I keep my API key out of the report?

Use Web.Contents with ApiKeyName = "api_key". Power BI then asks for a Web API credential, stores the key in its credential manager, and adds it to each request, so the key never appears in your M code or the shared .pbix file.

Does this work in Excel, dataflows, or Microsoft Fabric?

Yes. The same Power Query M runs in Excel's Get & Transform, Power BI dataflows, and Fabric Dataflow Gen2, so a query you build once can move between them.

How many Datpaq requests does a refresh use?

One request per Datpaq query per refresh. A report with three Datpaq queries refreshing eight times a day uses about 24 requests a day. Power BI Desktop may send a few extra requests while you edit in Power Query Editor.

Is there a Datpaq connector for Power BI?

A packaged Datpaq connector for Power BI Desktop is coming soon, so you'll be able to pick Datpaq straight from the Get data dialog. Everything on this page works today with Power BI's built-in Web connector.

Microsoft, Power BI, and Power Query are trademarks of the Microsoft group of companies. Datpaq is not affiliated with or endorsed by Microsoft.