Connect REST APIs to Excel Without VBA or Power Query

See everything Query Streams can do beyond this guide Get Started Free

Supports

+more

Live Data

Replace exports with on-demand SQL

Excel Sheets

BI & AI Analytics

Ask Nova, get SQL + charts

Meet Nova

Database REST API

One key per partner. No credentials shared.

Build an API

+more

Automation

Scheduled sync to 6+ platforms

Explore

+more

API to SQL

Query APIs with SQL, no code

Explore

+more

AI Database MCP

Claude, Cursor, ChatGPT & Grok talk to your data

Connect AI

Query Streams is a secure, real-time data integration platform that connects REST API data to Microsoft Excel and Google Sheets through SQL — no VBA macros, no Power Query M code, no manual JSON parsing. Learn more at QueryStreams.com and sign up for free to start querying APIs with SQL directly from your Excel workbook.

The API-in-Excel Problem

Excel users increasingly need data from REST APIs — Stripe payment records, HubSpot CRM contacts, Shopify orders, Google Analytics traffic metrics. According to Postman’s State of the API Report, the average organization now manages dozens of API integrations. But getting that API data into an Excel spreadsheet has always meant choosing between two imperfect options: VBA macros or Power Query. Both require significant technical effort, and neither gives you SQL-level querying over the results. If you have been searching for a way to call an API from Excel without writing code, you are not alone.

VBA Macros: Fragile and Hard to Maintain

The classic way to call a REST API from Excel is VBA. You write Sub procedures using XMLHTTP or WinHTTP objects to construct HTTP requests, set headers, pass authentication tokens, send the request, and parse the JSON response. The problem: VBA has no native JSON parser, so you either install a third-party library or write your own parsing logic. Error handling is minimal — a single API schema change, an expired OAuth token, or a rate limit response can break the entire macro silently. Pagination requires manual cursor or offset logic. There is no caching, no encryption, and no way to run SQL against the results. For a one-time data pull from a single endpoint, VBA works. For production workflows that multiple team members depend on, VBA macros become a maintenance liability that only the person who wrote them can debug.

Power Query: Limited REST API Support

Power Query’s Web.Contents function can call REST APIs, but the limitations are significant for anything beyond basic GET requests. OAuth 2.0 support is incomplete — many APIs, including Stripe and HubSpot, require custom token refresh flows that Power Query’s M language handles poorly or not at all. Pagination requires recursive function calls in M code, which is non-trivial for most Excel users. There is no built-in rate limiting management. Complex JSON responses with nested arrays and objects require multiple Transform and Expand steps. And Power Query has no SQL layer — you get M language transformations, not SQL JOINs, CTEs, or window functions. Power Query is a strong tool for connecting to databases and flat files. As a REST API connector for Excel, it falls short quickly when the API requires OAuth, pagination, or nested data structures.

How Query Streams Connects REST APIs to Excel

Query Streams takes a fundamentally different approach to Excel API integration. Instead of making you write VBA macros or wrestle with Power Query M code, it provides pre-built API connectors that normalize REST API data into SQL-queryable tables. The Query Streams Network Agent runs inside your network, syncs API data into an encrypted DuckDB cache, and the Microsoft Excel add-in lets you run SQL queries against that cached data — or pick from 20-50 pre-built queries per connector without writing any SQL at all.

6 Pre-Built API Connectors with Encrypted Caching

Where VBA and Power Query require you to configure every API from scratch, the Query Streams API Connector ships with 6 pre-built integrations that are ready to use in about 5 minutes each: Stripe (payments, subscriptions, invoices, refunds), HubSpot (contacts, deals, companies, pipelines), Shopify (orders, products, customers, inventory), Google Analytics 4 (traffic, events, conversions, user behavior), Google Search Console (search queries, pages, click-through rates, impressions), and ShipStation (shipments, orders, carriers, fulfillment). Each connector handles authentication, pagination, rate limiting, and data normalization automatically — the exact things that make VBA macros and Power Query M code so difficult to maintain.

All synced API data is stored in a local DuckDB cache on the Network Agent, encrypted at rest with AES-256-GCM. Per-table sync scheduling lets you set different refresh intervals for different API endpoints — sync high-priority tables like Stripe charges every 15 minutes while less critical tables sync daily. Per-table data retention gives you control over how long cached data is kept: 1 day, 7 days, 30 days, 90 days, 1 year, or forever. This architecture reduces API call volume, eliminates rate limit headaches, and means your SQL queries run against local data at database speed rather than waiting for live API round-trips. Your API credentials (tokens, keys) are stored locally on the Agent and never transmitted to the Query Streams cloud.

SQL Over API Data: Query, Don’t Parse

The core difference between Query Streams and VBA or Power Query for REST API access in Excel is what happens after data arrives. With VBA, you get a raw JSON string that you parse character by character. With Power Query, you expand nested columns through multiple transformation steps. With Query Streams, each API’s data is automatically normalized into SQL-queryable tables. You write standard SQL — JOINs across API endpoints, aggregations, window functions, CTEs, subqueries — the full SQL language against your API data.

For example, to analyze Stripe revenue by product with refund rates, a VBA approach requires multiple separate HTTP calls across different Stripe endpoints, manual JSON parsing for each response, and spreadsheet formulas to combine the results. With Query Streams, you write a single SQL query that JOINs stripe_charges, stripe_products, and stripe_refunds tables — and the result streams into your Excel workbook instantly. Query Streams also supports parallel query execution: launch multiple saved queries into multiple worksheet tabs at the same time and the Agent streams each concurrently, regardless of result size.

Nova AI: Describe Data, Get SQL

Not everyone on your team knows SQL, and not everyone should have to. Nova AI bridges the gap between plain English and validated SQL. Describe what you need — “show me Stripe revenue by product for the last 90 days with refund rates” — and Nova reads your actual API table schema, generates dialect-specific SQL, validates it, and executes the query live. Nova works with both database tables and API connector tables, so an analyst can ask questions across Stripe payment data and a PostgreSQL accounting database in the same conversation. For Excel users who have been relying on VBA macros or Power Query as their API connector, Nova eliminates the need to understand JSON structures, API documentation, or SQL syntax entirely.

Don’t know SQL? Nova AI builds the query for you.

Try Nova

1

Describe what
data you need

Nova reads schema
& builds the SQL

Save & run from
Excel or Sheets

I need total Stripe revenue by product for last quarter, broken down monthly. It’s for our Excel sales dashboard.

Found stripe_charges and stripe_products in your API connector schema. Here’s the query — run it to preview results, then save it to your library for your Excel dashboard.

SQL Results

Copy Run Save

SELECT
    p.name                          AS product,
    DATE_TRUNC('month', c.created)  AS month,
    SUM(c.amount) / 100.0           AS revenue
FROM   stripe_charges   c
JOIN   stripe_products  p ON c.product_id = p.id
WHERE  c.created >= DATE_TRUNC('quarter', NOW() - INTERVAL '3 months')
GROUP BY product, month
ORDER BY month, revenue DESC

Query Streams vs VBA vs Power Query

The comparison below shows how Query Streams’ API connector for Excel differs from VBA macros and Power Query for connecting REST APIs to a spreadsheet. VBA and Power Query offer flexibility for ad-hoc API calls, but Query Streams provides a managed, SQL-first approach with pre-built connectors, caching, and AI assistance.

The Query Streams Network Agent installs on Windows, Linux, or macOS and makes outbound-only connections — no inbound firewall rules needed. Deploy multiple Agents across your entire infrastructure: on-premise servers, AWS EC2, Azure VMs, Google Cloud, or any environment globally. All agents self-maintain with automatic updates and present their data sources as a unified dropdown list in the Excel add-in or Google Sheets add-on. The automation engine can also sync query results on a schedule to Airtable, Smartsheet, SeaTable, Baserow, and Anvil.Works — with both Append mode (10-150x faster incremental updates) and Full Sync mode (drift correction).

Frequently Asked Questions

Get Started

Related guides: API Connector | Databases in Microsoft Excel | Text to SQL with Nova AI | Automation and Integration | All Features

Category: Articles

Tags: API Connector, Excel, REST API, VBA Alternative, Power Query Alternative, Stripe, HubSpot, Shopify

Meta Description: Connect REST APIs to Excel without VBA. SQL over Stripe, HubSpot, Shopify. Try free.