Beta

Your data, yours to take

What qloudpulse holds about your spend is yours, and you should be able to take it out whenever you want, in formats other tools read, without asking us. The API at api.qloudpulse.com is where that happens: your scripts read every report and take your whole bill through it with a key of your own, and your pipelines send changes to it, in every plan.

What works today

Every route is under /v1, and the contract describes each one in OpenAPI 3.1: api.qloudpulse.com/v1/openapi.json. Point a client generator or an AI assistant at it.

  • POST /v1/events marks a release, deploy, incident or config change on your cost charts. Change events has the fields and a command for each CI system.
  • POST /v1/estimates prices an infrastructure change before it is applied, which is what qloudpulse estimate sends from a pull request.
  • POST /v1/estimates/catalogue says which resource types the estimate prices and what to send for each. It needs no token.
curl -fsS https://api.qloudpulse.com/v1/events \
  -H "Authorization: Bearer $QLOUDPULSE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"title": "checkout v2.31.0", "type": "release", "service": "checkout"}'

The first addresses, app.qloudpulse.com/api/report/public/events and …/estimates, keep working, so nothing you have set up needs to change.

Tokens

Every route takes a token of your company's own as Authorization: Bearer …. A sign-in to the app does nothing on the API, and the API sets no cookies.

  • Source tokens (qpev_…) write. An admin makes one per sender, such as a CI pipeline or Argo CD, under Settings, Events. It sends events and estimates and reads nothing, so a pipeline's token that leaks cannot read your costs.
  • API keys (qpk_…) read. An admin makes them under Settings, API keys, each reading everything your company has and expiring within a year. Keys that read only what one group may see are Coming

We keep only a hash of each token, so we cannot show one again: it is shown once, when it is made. Rotating one replaces it at once, and removing one refuses it. A token that is wrong, rotated or removed gets the same 401, which does not say which.

Reading your data

With an API key, GET /v1/reports lists the reports your company can read, as the app does, with what each can be grouped by and what it holds. GET /v1/reports/{report} gives a report's rows for the window you ask, grouped and filtered as you ask: the same rows as the page's CSV download, as JSON, or as CSV with Accept: text/csv.

curl -fsS "https://api.qloudpulse.com/v1/reports/$REPORT?from=2026-11-01T00:00:00Z&to=2026-11-17T00:00:00Z" \
  -H "Authorization: Bearer $QLOUDPULSE_API_KEY" -H "Accept: text/csv"

$REPORT is a report's id from GET /v1/reports. Add groupBy with one of the dimensions it lists to split the rows, and filter to keep only some.

A request gives 1,000 rows, or up to 10,000 if you ask with limit. When the window holds more, the answer says so with truncated (X-Truncated in CSV): ask for a shorter window, filter, or group by less. Reading your change events back, GET /v1/events, is Coming

Amounts are decimal strings with their currency, and times are ISO 8601 in UTC, so nothing is rounded on the way out.

Taking all of it

POST /v1/exports builds a file in the background for whole months, up to 13, and answers at once. GET /v1/exports/{id} says where it stands, and once it is ready GET /v1/exports/{id}/file downloads it with the same key. A file is kept for 7 days.

curl -fsS https://api.qloudpulse.com/v1/exports \
  -H "Authorization: Bearer $QLOUDPULSE_API_KEY" -H "Content-Type: application/json" \
  -d '{"kind": "focus", "from": "2026-01", "to": "2026-10"}'
  • Your bill as FOCUS ("kind": "focus"), every cloud in it, as one gzipped CSV. FOCUS is the FinOps Foundation's open format for cloud bills, and the one qloudpulse reads other clouds' bills in. qloudpulse keeps the bill by day, so each row is a day of one account, service, region and charge category, and the columns about single resources, SKUs, quantities and commitment discounts are empty.
  • Everything ("kind": "everything"): every report's rows by day, the FOCUS bill, your change events, budgets, allocation rules and chargeback statements, in one zip with a README that says what is in it. It is what you take with you if you leave. Alerts are not in it: they are each person's own.

One export at a time per company, and a file of at most 50 MB compressed; for more, ask for fewer months at a time. Without a script, an admin makes the same exports under Settings, Export your data, and the card that deletes your company sends you there first: download your export before you delete, as nobody can sign in afterwards.

How it behaves

  • It only grows. /v1 changes only by adding routes, optional fields and values, so a client has to ignore what it does not know. Anything else would be /v2, and /v1 would keep answering for a year after it, with a Sunset date on every answer.
  • From any origin. Your own browser tools can call it: the API answers any origin, without cookies, so a token is sent only when your own code sends it.
  • Refusals say why. As problem details (RFC 9457), with what to change. Past a limit, the answer is 429 with Retry-After.
  • Self-hosted too. An install serves the same /v1 routes on its own host, so a script written for one runs against the other.
  • Apart from every other company. A token names its company, and every read through it sees only that company's data.

Questions

What does it cost?

Nothing: the API is in every plan. It reads what qloudpulse already holds, so it adds nothing to your AWS bill either.

Is there an SDK?

Not yet. The OpenAPI contract is enough for a client generator, and curl is enough for most pipelines.

Can I read my users or company settings?

Not through the API. It holds your spend and what you have set about it; who is in your company stays on the company page.

Sign up