EcomSolo Developer API

The EcomSolo Developer API lets you pull your consolidated, multi-store Shopify data — sales, shipping, orders, customers, inventory and more — programmatically, instead of exporting CSVs by hand. Point one HTTP request at EcomSolo, write a short SoloQL query, and get back a clean, currency-normalised table across every connected store.

The base URL is https://api.ecomsolo.com, and every request authenticates with a single bearer token:

Authorization: Bearer esk_live_...

What you can do

  • Consolidate every store in one query — one request returns totals across all your shops, or broken out per store, with money auto-converted to a single currency so the numbers are comparable.
  • Query with SoloQL — a compact, readable query language built for commerce reporting (FROM sales SHOW total_sales GROUP BY store SINCE -30d).
  • Discover your data — a self-describing catalog endpoint lists every dataset and field, so your integration can adapt without hard-coding schemas.
  • Get JSON or CSV — the same query returns structured JSON, or tabular CSV with an Accept header, ready for a spreadsheet or a warehouse load.
  • Scale without surprise fees — rate limits scale with your plan, and there are no per-call or overage charges, ever.

Get started

  • Getting started — create a key and make your first request in a few minutes.
  • Authentication — keys, the bearer header, scopes, and keeping secrets safe.

Core concepts

  • Querying with SoloQL — the query language, multi-store consolidation, dates, and worked examples.
  • Fetching records — get the orders, customers and products themselves with a plain GET, filtered and paged. No query language needed.
  • Running exports — trigger a saved export from code, poll it, and download the file. The way to pull large volumes.
  • Datasets and fields — what you can query, and how to discover every field.
  • Rate limits — per-plan limits, headers, and handling a 429.

AI assistants

  • MCP server — connect Claude to your account and ask for consolidated numbers in plain language. Read-only, same key, same limits.

Reference

  • API reference — every endpoint, parameter, and the error model.
  • Recipes — practical, copy-paste integrations: a morning pull, Google Sheets, and a BI warehouse feed.
  • Acceptable use — the rules that come with a key: onward transfer, customer personal data, AI/ML training, and retention.