Can Apipheny query API data with SQL syntax?

No. Apipheny retrieves raw JSON or XML from REST APIs and flattens it into Google Sheets cells. There is no SQL layer, no query builder, and no way to write JOINs, aggregations, or CTEs against API data. Query Streams' API Connector normalizes API responses into SQL-queryable DuckDB tables, giving you full SQL power over API data.

Which APIs does Query Streams support as pre-built connectors?

Query Streams currently offers 6 pre-built API connectors: Stripe (payments, subscriptions, invoices), HubSpot (contacts, deals, companies), Shopify (orders, products, customers), Google Analytics 4 (traffic, events, conversions), Google Search Console (search queries, pages, click-through rates), and ShipStation (shipments, orders, carriers). Each connector normalizes API data into SQL tables and includes 20-50 pre-built queries in the Query Library.

How does the encrypted DuckDB cache work?

Each API connector syncs data from the API into a local DuckDB database on the Network Agent. This cache is encrypted at rest with AES-256-GCM . You configure per-table sync intervals (how often the Agent pulls fresh data from the API) and per-table data retention (how long cached data is kept: 1 day, 7 days, 30 days, 90 days, 1 year, or forever). Your SQL queries run against this local cache at database speed, not against the live API, which eliminates latency and rate limit concerns.

Does Query Streams work with Google Sheets like Apipheny does?

Yes. Query Streams has a native Google Sheets add-on and a native Microsoft Excel add-in. Users select a saved query from their library, adjust any available filters, and click run for live data on-demand. Unlike Apipheny, Query Streams also supports Excel, so teams that use both spreadsheet platforms only need one tool.

Do I need to know SQL to use Query Streams' API Connector?

No. Each connector ships with 20-50 pre-built queries in the Query Library that you can run directly from Google Sheets or Excel without editing any SQL. Nova AI can also generate SQL from plain English descriptions. Describe what data you need -- "show me Shopify orders by product category for Q1" -- and Nova writes, validates, and executes the query. You can also share queries with team members who run them without seeing the SQL at all.

How does pricing compare between Apipheny and Query Streams?

Query Streams offers a free tier and flat-rate paid plans that include database connectors, API connectors, and unlimited query executions under one subscription. You get 10 database dialects and 6 API connectors at the same price. See Query Streams pricing for current details. Apipheny offers a free tier with limited API calls and paid plans for higher volumes.

What if my API is not one of the 6 pre-built connectors?

Query Streams' API Connector currently supports Stripe, HubSpot, Shopify, GA4, GSC, and ShipStation. If you need to connect to an API that is not on this list, Apipheny or another generic API tool may be more appropriate for that specific endpoint. However, Query Streams also connects to 10 SQL databases, so if the data you need is available in a relational database, you can query it directly without going through the API layer.

Can I share API queries with people who do not have a Query Streams subscription?

Yes. Save any query -- whether it runs against a database or an API connector -- and share it with anyone. The recipient opens it in the Excel or Google Sheets add-in, adjusts any available filter values, and clicks run. They get live results without seeing the SQL code, schema, or credentials. Apipheny has no concept of sharing an interactive, runnable query; it only produces static spreadsheet output.

Can I use Apipheny and Query Streams together?

Yes. Some teams use Apipheny for ad-hoc calls to niche REST APIs and Query Streams for structured SQL access to Stripe, HubSpot, Shopify, GA4, GSC, ShipStation, and their SQL databases. The two add-ons can coexist in Google Sheets without conflict. Over time, as Query Streams adds more API connectors, you may find less need for the manual approach.