Skip to main content
If you split costs across teams or clients, you’ll want the usage figures in your own systems rather than reading them off a page.

​
Your usage

Returns usage across every project you can see, grouped by day, for the last 30 days.

​
Narrowing it

If you send both since and days, since wins and days is ignored. The response tells you which was used: since comes back as the effective lower bound, and days comes back as null whenever since was applied. Check that field rather than assuming your days took effect.

​
Incremental exports

For a nightly job, keep the since value the last run returned and pass it back next time. That gives you exactly the rows you haven’t seen, with no overlap to de-duplicate and no gap if a run is late.

​
One task’s usage

Grouped by capability class — useful when you want to know what a specific piece of work cost.

​
Organization usage

Every billed event attributable to the organization, one row per request, so you can attribute spend by member or project in your own reporting. Owners and admins only.