Rate limits

API requests are rate limited per API key, using a per-minute sliding window. The limit scales with your plan.

Limits by plan

Plan	Requests per minute
Advanced	30
Business	60
Business 200K	90
Business 300K	120
Unlimited	180

info

There are no per-call charges and no overage fees — ever. If you need more throughput, the limit rises with your plan tier rather than billing you per request.

Rate-limit headers

Every /v1 response includes an X-RateLimit-Limit header with your key's per-minute ceiling. When you exceed the limit, the response is 429 Too Many Requests and includes a Retry-After header, in seconds — wait that long, then retry.

X-RateLimit-Limit: 60
Retry-After: 12

note

Only X-RateLimit-Limit (on every response) and Retry-After (on a 429) are provided. There are no X-RateLimit-Remaining or X-RateLimit-Reset headers, so pace your requests against the per-minute limit rather than a live remaining count.

Handling a 429

When you get a 429, read the Retry-After value and sleep for that many seconds before retrying. A small helper keeps this out of your query code:

JavaScript
Python
cURL

async function query(body, key) {
  while (true) {
    const res = await fetch("https://api.ecomsolo.com/v1/query", {
      method: "POST",
      headers: {
        Authorization: `Bearer ${key}`,
        "Content-Type": "application/json",
      },
      body: JSON.stringify(body),
    });

    if (res.status === 429) {
      const wait = Number(res.headers.get("Retry-After") || 1);
      await new Promise((r) => setTimeout(r, wait * 1000));
      continue;
    }

    return res.json();
  }
}

import time
import requests

def query(body, key):
    while True:
        res = requests.post(
            "https://api.ecomsolo.com/v1/query",
            headers={"Authorization": f"Bearer {key}"},
            json=body,
        )
        if res.status_code == 429:
            wait = int(res.headers.get("Retry-After", "1"))
            time.sleep(wait)
            continue
        return res.json()

# curl --retry respects Retry-After when combined with --retry-all-errors
curl https://api.ecomsolo.com/v1/query \
  --retry 5 --retry-all-errors \
  -H "Authorization: Bearer esk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"query": "FROM sales SHOW total_sales GROUP BY store SINCE -30d"}'

Staying under the limit

Batch your reporting into fewer, larger queries rather than many small ones — one GROUP BY store query returns every store at once.
Cache results you re-use within the same minute instead of re-querying.
Spread scheduled jobs out over the minute rather than firing them all at once.