Skip to main content

iApp Core API — your usage reports and credit balance as JSON, for your own dashboards

· 3 min read
Kobkrit Viriyayudhakorn
Kobkrit Viriyayudhakorn
CEO @ iApp Technology

iApp Core API — your usage, your credits, your dashboard

You asked for it constantly: "Can I get my usage data out of the dashboard and into my own systems?" Now you can. The new Core API exposes your iApp usage reports and credit balance as clean, read-only JSON — so you can build exactly the dashboard, alert, or cost report your team needs, with the API key you already have.

What you can pull​

  • GET /credits — your remaining credit balance, real-time
  • GET /usage/summary — total requests, credits spent, success rate, latency for any date range
  • GET /usage/timeseries — chart-ready buckets by hour, day, week or month
  • GET /usage/services — per-service breakdown: requests, credits, latency, error rate
  • GET /usage/records — the raw call log with filters (date range, service, method, status, minimum cost), sorting (time, credits, latency, status) and pagination up to 1,000 rows per page

One header, that's the whole integration:

curl "https://iapp.co.th/api/core/v1/usage/summary?startDate=2026-08-01" \
  -H "apikey: YOUR_API_KEY"

What people are building with it​

📉 Low-balance alerts — a five-line cron job that pings Slack before credits run out, instead of finding out from an HTTP 402.

📊 Team cost dashboards — pull /usage/timeseries into Grafana or Google Sheets and see exactly which day that batch job doubled your OCR bill.

🧾 Client billing — agencies running iApp APIs for multiple projects use one key per project, then split costs with /usage/records' per-key prefixes.

🚨 Error monitoring — /usage/records?statusClass=4xx&sortBy=timestamp is your API-level error log, ready for your observability stack.

Safe by design​

We built this for the paranoid (that's a compliment):

  • Read-only. Every endpoint is GET. A leaked key can never create keys, spend credits, or change your account through this API.
  • No PII. Responses carry technical telemetry only — timestamps, endpoint paths, status codes, credits, latency. Never names, emails, user IDs, client IPs, or the contents of your requests. Query strings are stripped from paths and API keys appear only as 8-character prefixes, so even a leaked report leaks nothing sensitive.
  • Your data only. There is no parameter that reaches another account.
  • Rate-limited at 120 requests/minute per key — more than any sane dashboard needs.

And it's free: Core API calls don't consume credits.

Postman collection included​

Don't want to hand-write requests? Import our ready-made Postman collection — all six endpoints, ready-to-toggle filter examples, and 51 built-in test assertions (including automated checks that no PII and no full API key ever appear in a response):

Import the collection plus an environment, paste your API key into the apikey variable, and run the whole suite with the Collection Runner.

Monitored and transparent, like everything else​

The Core API joins our public status page under Core Services — the same 5-minute health checks as our 60+ AI APIs — and is listed on the live stats page alongside the rest of the platform.

Get started in 60 seconds​

  1. Grab your API key from API Key Management
  2. curl https://iapp.co.th/api/core/v1/ping -H "apikey: YOUR_KEY"
  3. Read the full documentation — parameters, examples in Python and Node.js, and a 20-line starter dashboard

Read the docs →