Most SQL-to-API stories start with “so first we built a small web service…” EQQ skips that. Every saved query is already a REST endpoint. You just turn it on.

The five-minute version

  1. Open the query you want to publish in Manage Queries.
  2. Switch to Query To JSON from the Data Visualization menu.
  3. Pick the query, click Generate.
  4. EQQ mints a URL like /api/usequery/42/execute and a sample curl.
  5. Create an API key under My Account → API Keys and pass it as X-API-Key.
Query To JSON - every query becomes a REST endpoint with no extra code.
Query To JSON - every query becomes a REST endpoint with no extra code.

Call it from anywhere

curl -H "X-API-Key: $EQQ_KEY" \
  -H "Content-Type: application/json" \
  -d '{"StartDate":"2026-01-01","EndDate":"2026-03-31"}' \
  http://your-eqq:8081/api/usequery/42/execute

The response is a JSON array of rows with typed columns. No server-side DTO, no controller, no Swagger fight. If you change the query, the endpoint just reflects the new shape.

Why this matters

  • Time to first byte: minutes, not sprints.
  • One source of truth: the data team owns the query, the app team owns the UI. They meet at the endpoint.
  • Security in the right place: API keys are scoped to roles; a rogue key cannot escalate.

Typical integrations in one afternoon

  • A Next.js dashboard pulling month-end numbers.
  • A Slack bot answering “how many open tickets?” from a query.
  • A scheduled job exporting compliance rows to SFTP nightly.

Want to see it live? Book a 30-minute demo - we connect EQQ to your database and build a query with you. Book a Demo →

Dive deeper in the Query To JSON docs.

Key Terms

  • DTO - Data Transfer Object - a class that carries data between application layers with no business logic.