A month's statement
A calendar month (UTC), whatever the periods of the account's subscription: the parts it is made of (the periods that have hours in it, and the hours in no period, which are the free plan's), each with, for every meter, what was used in it, what its stretch includes, what was past that, the price and the amount, what the lines come to at the prices, what of that the stretch's credit paid and what is left of it, and what is left to pay; each meter's line for the whole month; what the parts add up to, which is what the month's usage takes from the account's balance as far as the balance goes; the credit of the month, granted, used, gone to a plan the account moved up to and lapsed; the fees of the periods that began in the month; which Credits paid, by the kind of lot, what none has paid and is owed, and what none could pay and is written off; what was added to the balance in the month and what lapsed with it; what each project used, to be held against GET /v1/usage (from and to the month's) with that project's key; and what the account held at the month's end. A period that lies in two months has what it owes, and what its credit paid, split between their two statements so that the two add up to it, to the millionth of a dollar. The month that is not over yet is as it stands. A month that is over does not change in what was used and what it came to, unless usage of it comes in afterwards (a node that was away): then it is not closed until what it comes to is taken from the balance, and is closed again within seconds. What it says paid for it changes when something it owed is paid by Credits that came later. A month the account had nothing in has nothing used. Takes read.
https://api.glac.ai/v1/billing/statementAuthorization
Query parameters
Returns
200
The statement.
- written_off_usdnumberrequired
What the month's usage came to that no lot could pay and that is owed by nobody: what an account that held nothing used of the meters that are stopped (CPU time, memory, requests, traffic, logs kept, Drive writes and cold reads, Object Storage's class A and B requests) between what the stretch includes running out (a quantity, or the credit) and the stop taking hold. With
credits_debitedit isusage_usd, once a look has brought the ledger up to the statement. - paid_fromobjectrequired
Which Credits paid for the month's usage, by the kind of lot (
Lot.kind), and what none has paid (unpaid: it is owed, and the next Credits pay it first). They add up tocredits_debited. A kind that only a store from before plans included quantities has (month_grant,period_grant) is there where something of it paid; anddebt_written_offwhere what was owed for the month was written off when what the account stored had been deleted (it is among what adds up, and nobody paid it). - closedbooleanrequired
The month is over, what its usage comes to was taken from the account's balance as this statement has it (
credits_debitedandwritten_off_usdareusage_usd), and what was left of the lots that lapsed in it is written off. False for the month it is; false in the seconds after a month's end, until what was used in it is in the books (ten minutes at the most, when a node is not read); and false again while usage of the month that came in later waits to be taken, which is seconds.