Returns current Information Units (data units) for DataDelivery WS: request / response examples, which are remaining (if any) or N/A otherwise. If 0 is returned, usage limit is reached and no more calls will be processed. Processing or request is also not possible if requested number of data units is exceeding remaining Information Units (data units).
Returns number of consumed site units for given billing period. Number of consumed site units is grouped by data request summarization and data request period where each combination of data period and data summarization represents one type of site unit. The result is then presented in JSON format. For example:
which for billing period of March 2016 summarizes how many site units of each type were consumed, e.g. 10 units for type = "HISTORIC + MIN_15", 20 units for type = "RECENT + HOURLY" etc.
Only site unit types where count > 0 are included in the result.
Besides JSON (which is the default format), there are two other supported output formats: CSV and HTML You can specify output format of the request by additional request parameter "format". For example to get the example above in HTML you can use:
(thus including both HOURLY and MIN_15 for site with the same latitude / longitude)
Basic billing period is one month. When parameters "from" and "to" are used to specify billing periods longer than one month, first the partial results for each month will be calculated and then the partial results will be summed up for the final result. If the specified billing period is shorter than one month, or is not a whole multiple of a month then the last partial billing period will be adjusted to length shorter than one month.
RECENT and FORECAST site units charged in previous billing period won't be charged in the next billing period. That is to assure that each month of data (of type RECENT or FORECAST) is charged only once, regardless of during which billing periods the requests were made.
For example following RECENT request made during billing period of March 2016:
will be counted as 0 site units, because this site unit was already charged during March billing period.
Requests made during previous billing period do not affect billing of HISTORIC data.
DataDelivery unique information units API
Returns number of consumed unique information units in CSV format for given billing period as well as site coordinates (latitude, longitude) with associated unique information units spent for given location. The unique information API operates in two modes:
RECENT + HISTORIC access (default) = include all web service calls where "dateTo" of requested data is < today
FORECAST access = include all web service calls where "dateTo" of requested data is >= today
To request recent + historic access report for demo account (key = demo) and for September 2019 you can use following URL. Replace key with your account key (provided to you by sales person) to know consumption of your unique information units.
In order to get consumption report for different billing periods just replace "from" and "to" parameters in the url.
Unique information units
Unique information unit is unique combination of latitude + longitude + requested days of data. First time some unique combination of latitude, longitude and day is accessed via web service call this results in charge of one unique information unit. All subsequent calls for the same unique combination of latitude + longitude + day do not increase the consumption of unique information units. This is true even for calls made months apart, i.e. calles made during different billing periods - when accessing the same combination of latitude, longitude and day - the subsequent calls will be charged as 0 unique information units. If your request contains multiple days of data, each day is considered individually for its uniqueness.