Coming from StatHat? You're about five minutes from a live chart.

1. Get your EzStat API key

Sign up, then open the dashboard Settings page and copy your API key (about 30 seconds). The legacy /ez, /c and /v endpoints use this key; the newer v1 REST API uses a Bearer token generated in the same place.

2. Change one base URL

Most StatHat client libraries let you override the base URL, so this is often a one-line config change rather than a find-and-replace. If you hardcoded the host, the blunt swap is:

sed -i 's#api.stathat.com#api.ezstat.dev#g' your-code/

Or override the base URL in your client — the same languages StatHat shipped SDKs in:

# curl
curl -X POST https://api.ezstat.dev/ez -d "ezkey=KEY" -d "stat=signups" -d "count=1"

// Go — set the base URL to https://api.ezstat.dev
// Python — requests.post("https://api.ezstat.dev/ez", data={...})
// Node — fetch("https://api.ezstat.dev/ez", { method: "POST", body })
// Ruby — Net::HTTP.post_form(URI("https://api.ezstat.dev/ez"), ...)

Then swap the StatHat key for your EzStat key — your old StatHat identity is not a credential here.

3. POST one point and watch it land

# BEFORE — your existing StatHat call
curl -X POST https://api.stathat.com/ez \
  -d "ezkey=YOUR_STATHAT_KEY" -d "stat=signups" -d "count=1"

# AFTER — EzStat. Change the host, use your EzStat key.
curl -X POST https://api.ezstat.dev/ez \
  -d "ezkey=YOUR_EZSTAT_KEY" -d "stat=signups" -d "count=1"

# → {"status":200,"msg":"ok"}   <- the verdict is in the BODY. Read it. See step 4.

Refresh your EzStat dashboard — your stat auto-created and your first point is on the chart. That's it — you're live.

4. Check the response BODY, not the status code

# The HTTP code is 200 either way. The BODY is the verdict.
curl -s -X POST https://api.ezstat.dev/ez \
  -d "ezkey=YOUR_EZSTAT_KEY" -d "stat=signups" -d "count=1"

# → {"status":200,"msg":"ok"}                   recorded
# → {"status":"error","msg":"invalid ezkey"}    NOT recorded — and still HTTP 200

# Make it fail loudly in a script:
curl -s -X POST https://api.ezstat.dev/ez \
  -d "ezkey=YOUR_EZSTAT_KEY" -d "stat=signups" -d "count=1" \
  | grep -q '"status":200' || { echo "EzStat DROPPED the point"; exit 1; }

# Same check with jq:
curl -s -X POST https://api.ezstat.dev/ez \
  -d "ezkey=YOUR_EZSTAT_KEY" -d "stat=signups" -d "count=1" \
  | jq -e '.status == 200' >/dev/null || { echo "EzStat DROPPED the point"; exit 1; }

# WRONG — 200 means "the request reached us", not "the point was recorded"
requests.post(EZSTAT_URL, data=payload).raise_for_status()

# RIGHT — read the body; on a rejection status is the string "error"
r = requests.post(EZSTAT_URL, data=payload)
if r.json().get("status") != 200:
    raise RuntimeError(f"EzStat dropped the point: {r.json().get('msg')}")

5. Confirm the points are arriving — not just accepted

curl -fsSL https://ezstat.dev/tools/ezstat-verify.py -o ezstat-verify.py
python3 ezstat-verify.py --key YOUR_EZSTAT_KEY

6. Endpoint compatibility

The StatHat wire format maps one-to-one. Stats auto-create on the first POST — no pre-registration.

The one gotcha: Classic /c and /v take the API key in ukey — EzStat maps ukey to your EzStat API key. Full reference in the docs.

About the t param: /ez, /c and /v reject a t more than five minutes ahead of server time with a 400, and the check runs per write — one drifting host loses exactly that host's points while every other host looks healthy. Backfill any distance inside the accepted window; the past-side floor (2000-01-01) is a bug detector for uninitialised variables, not a backfill bound.

About the ikey param (optional, /ez): dedup keys on stat + timestamp + ikey (the sole index is migration 043), so a retry is only recognised as the same point when you send the same t and ikey on every attempt. An ikey alone is not enough: without t, the server stamps each attempt's arrival time, so a retry lands on a different timestamp and is stored — and billed — a second time. Same rule as /docs#replay-semantics.

# safe to retry: identical t + ikey on every attempt
curl -X POST https://api.ezstat.dev/ez \
  -d "ezkey=YOUR_EZSTAT_KEY" -d "stat=orders" -d "count=1" \
  -d "t=1750000000" -d "ikey=order-9831"

7. Bring your history (optional)

A live token-pull is not possible — StatHat's API is offline. But if you saved your CSV or JSON export before shutdown, upload it and EzStat recreates each stat and backfills its points. Use ?dryRun=1 to preview first.

• → POST your export to /api/v1/import/stathat or use the dashboard import UI.
• → Limits: 8MB / 500,000 points per file, quota-trimmed. Backfilling into an existing stat does not cost stat quota.
• → Or backfill live points by passing a unix t timestamp on ingest.
• ◦ Not a one-click bulk importer — it recreates stats from the file you upload.

Bringing a large history or a team? We'll help you migrate.

8. Troubleshooting

Migration questions