Your database, a live REST API. In about 90 seconds.
Turn any saved query into a secure, rate-limited REST endpoint — call it yourself from a dashboard, script or internal app, or hand a key to a partner. Every key is scoped to one query, read-only by default, and your database credentials never leave your network — no gateway to host, no middleware to write.
One request. Live rows. No credentials exchanged.
You — or a partner — call a stable URL with a personal key. Query Streams runs your saved query through the Network Agent, enforces read-only, meters the call, and streams JSON back — while your database stays sealed inside your network.
curl https://api.querystreams.com/v1/endpoints/8f3c1a… \
-H "X-API-Key: qsapi_8Fa3kZ…" \
-G --data-urlencode "region=EMEA"{
"endpoint": "emea-active-accounts",
"rows": [
{ "account": "Northwind GmbH", "mrr": 8400, "status": "active" },
{ "account": "Contoso SARL", "mrr": 6100, "status": "active" },
… 140 more rows
],
"meta": { "source": "PostgreSQL", "cached": false }
}The partner never saw the SQL, never got a database credential, and can only run this one query — and you see every call in your activity ledger.
An illustrative request with sample data.
You share the capability — not the keys to the kingdom.
Most database-API tools expose your whole schema and let consumers browse your tables. Query Streams is the opposite: a single saved query defines exactly what an endpoint returns — and your partner gets those rows and nothing else about how they were produced.
What your partner gets
- A stable endpoint URL + their own API key
- Live JSON / CSV rows, read-only
- Filter parameters that reshape the query — without exposing it
What they never get
- Your SQL, schema or table names
- A database credential or connection string
- Any write access — or a path into your network
Why teams pick it over PostgREST & DIY gateways
You can stand up PostgREST or an Express + Knex API in an afternoon. Here’s what that DIY path can’t match when you share data with someone outside your company.
Nothing exposed to the internet
The Network Agent opens one outbound connection and dispatches queries from inside your network. No firewall port, no read replica, no VPN, no public API server to harden — the pattern security teams approve.
One key per partner, not a shared secret
Every recipient gets their own qsapi_* key, their own rate limit, and their own line in your usage ledger. Revoke one in a click without touching the others — no key-management service to build.
Read-only — and the SQL stays yours
Every call passes a hardcoded read-only validator (SELECT / WITH / EXPLAIN). The recipient runs the endpoint but never sees the query behind it and can’t change it. You share the capability, not the blueprint.
Everything you’d bolt onto a DIY API — built in
An endpoint isn’t just a URL. Each one ships with the developer-experience layer you’d otherwise assemble from a gateway, a docs generator, an auth service and a metering pipeline.
Auto-generated OpenAPI 3.1
Every endpoint emits a real spec at /openapi.json from the agent’s schema scan — drop it into Swagger UI, a client generator, or an LLM. No hand-written docs.
In-browser test sandbox
A “try it now” panel sits next to every endpoint — fire a call, pass filters, and see live rows, status, latency and compressed-vs-decompressed size without leaving the portal.
JSON, NDJSON, CSV & streaming
Return JSON, newline-delimited NDJSON or CSV per request, and stream large result sets so a job doesn’t wait on the whole payload. Optional LZ4 makes analytics responses 3–5× smaller on the wire.
Permanent, expiring & self-destruct
Give any endpoint a lifetime: keep it permanent, have it expire on a date, or set a call budget that self-destructs after the last allowed call — perfect for a single secure data drop.
Rate limits, quotas, IP & CORS locks
Stack two-tier rate limits (per key and per endpoint), a monthly byte quota, a per-key IP allowlist and a per-endpoint CORS origin list — tighten the blast radius before you ever share a key.
Drops into Power BI & Tableau
A clean REST API with an OpenAPI 3.1 spec and JSON/CSV output imports straight into Power BI and Tableau via their web/REST connectors — ideal for your own internal dashboards and reports — plus filter parameters (region, since, tenant) for you or your recipients to shape the data.
From a saved query to a shared endpoint, in four steps
The old way is a credential, a replica, or a nightly export. This is a live, read-only endpoint instead.
Pick a saved query
Write it once in Query Builder against any connected database, with optional filter parameters your partner can pass in.
Flip it to an endpoint
Name it, set rate limits and a lifetime — permanent, expiring or self-destruct — and you get a stable api.querystreams.com URL.
Share it — two ways
Email a magic-link invite and they claim a tracked, revocable key in seconds, or mint a service key to hand straight to a script.
Call live data
Your dashboard, an internal app, an n8n flow, a spreadsheet — or a partner’s app — hits the endpoint on demand. You watch every call and revoke access anytime.
Query Streams vs PostgREST, Hasura & DIY gateways
The big platforms do far more than we do — we’re not out-featuring them. We make one job, securely sharing a query with a partner, dramatically simpler and cheaper.
PostgREST / Hasura / DIY gateway
- Your database or a public API server must face the internet
- You host, scale, patch and renew TLS on the whole stack
- You build key management, rotation & per-key metering
- Your schema is the API — partners browse your tables
- Often one database engine (PostgREST = Postgres only)
Query Streams API Platform
- Nothing exposed — outbound-only agent, no port, no VPN
- We host the API, keys, quotas, TLS & scaling — you run an agent
- One key per partner, ledgered, one-click revoke
- A query — not your schema — defines what the endpoint exposes
- 11 database engines, on-prem or cloud, from one agent
Full API gateways (Kong, Apigee, CData) are powerful and have their place — Query Streams doesn’t replace them. It’s the simpler, more affordable path for one job: sharing live data with named partners, vendors and clients without standing up — or paying for — all of that.
Every popular SQL database, exposed as a REST API
38 database connectors on the same Network Agent that already powers your Excel, Sheets and MCP — no extra setup. A federated query publishes the same way: your consumer calls one endpoint and receives rows already joined across several databases, with no idea there was ever more than one.
API Platform FAQ
Do my partners need an account or a database credential?
Neither. Invite a person by email and they claim a magic link — a free org is created in seconds and they get their own tracked key (best for attribution and one-click revoke). Or mint a service key and hand it straight to their script — no account needed. Either way they never get a database credential, a connection string, or the SQL behind the endpoint; they just call a stable URL with their X-API-Key and get live rows.
How do partners change the data without seeing the query?
Through filter parameters. You expose the variables in your saved query — region, since, tenant — as query-string parameters. The recipient passes values to reshape what the query returns, but never touches or sees the SQL itself. The query controls exactly what the endpoint can expose; the filters just steer it within those bounds.
Do I have to host or maintain anything?
No. We host the API, the keys, the quotas, the TLS and the scaling. You just run the lightweight, outbound-only Network Agent inside your network — there’s no API gateway, rate-limiting middleware, read replica or Express server to deploy or patch.
What if a recipient tries to write or delete?
They can’t. Every call runs through a hardcoded read-only validator at the agent — only SELECT, WITH and EXPLAIN are accepted, and the recipient can only run the one saved query behind the endpoint. There’s no way to write, drop, alter, or reach any other table.
Which plans include the REST API, and what do recipients pay?
The Database REST API is included on the Business and Enterprise plans, with a 30-day free trial on signup and no credit card required. Your recipients pay nothing to consume an endpoint — usage is billed to your account on compressed bytes (the wire size shown in your ledger), with no per-seat fees.
Share live data in 90 seconds — not your credentials.
Turn a saved query into a secure, per-recipient REST endpoint. Read-only, revocable, and nothing leaves your network.
English 
Spanish 
German 
French 
Portuguese 
Japanese 
Korean 
Chinese 
Italian 
Dutch 
Indonesian 
Polish