We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
From official Octopus GraphQL usage:
query getMeasurements($accountNumber: String!, $first: Int!, $utilityFilters: [UtilityFiltersInput!], $startOn: Date, $endOn: Date, $startAt: DateTime, $endAt: DateTime, $timezone: String, $cursor: String) { account(accountNumber: $accountNumber) { properties { id measurements( first: $first utilityFilters: $utilityFilters startOn: $startOn endOn: $endOn startAt: $startAt endAt: $endAt timezone: $timezone after: $cursor ) { edges { node { value unit ... on IntervalMeasurementType { startAt endAt __typename } metaData { statistics { costInclTax { costCurrency estimatedAmount __typename } value description label type __typename } __typename } __typename } __typename } pageInfo { hasNextPage hasPreviousPage startCursor endCursor __typename } __typename } __typename } __typename } }
Variables:
accountNumber: "A-******" endAt: "2024-10-19T22:59:59.999Z" first: 60 startAt: "2024-10-18T23:00:00.000Z" timezone: "Europe/London" utilityFilters: { electricityFilters: { deviceId: "******" marketSupplyPointId: "*****" readingDirection: "CONSUMPTION" readingFrequencyType: "HOUR_INTERVAL" }
The returned value contains the parsed standing charge and consumption cost, so we don't have to fetch and parse the raw readings and lookup tariffs.
The text was updated successfully, but these errors were encountered:
ryanw-mobile
No branches or pull requests
From official Octopus GraphQL usage:
Variables:
The returned value contains the parsed standing charge and consumption cost,
so we don't have to fetch and parse the raw readings and lookup tariffs.
The text was updated successfully, but these errors were encountered: