Get a generation or orchestration-run billing receipt

GET 
/v1/projects/:project_id/usage/receipt

What one occurrence was billed, line by line: per-event line items with their measured components and unit prices, a per-meter-type split, and the totals. Pass generation_id for one generation, or orchestration_run_id for a receipt summed across every event the run metered. Exactly one of the two is required.

This is the itemisation behind a single number — where the meter says a window cost $12.40, a receipt says which components of which call made up one occurrence of it. On an orchestration-run receipt every line carries node_id, so grouping by it gives the per-node cost the total hides; a retried node contributes one line per attempt, which is the intended reading for spend.

Request

Responses

200

The receipt.

400

Neither selector was given, or both were.

401

Missing or invalid credentials.

404

No usage was recorded for that id in this project — which is also the answer for an id belonging to another project.