Can we get access to the OVO energy online account API to download our smart meter usage data?

Sure. That’s where the data come from to populate the various bits of the account site. Here are a few more sources that work for me:

https://smartpaymapi.ovoenergy.com/usage/api/monthly/{account}?date=2022

https://smartpaymapi.ovoenergy.com/pace/recommended-dds/v1/{account}/projected-costs?limitNextYear=true

 https://smartpaymapi.ovoenergy.com/rlc/rac-public-api/api/v5/supplypoints/electricity/{MPAN}/meters/{MSN}/readings?from=2016-09-09

This isn’t real-time; I think the newest data are from the last daily refresh, usually shortly after 01:00 each day. So today’s data won’t ever be available.

[What I’d really like is for an Excel guru to tell me how to include the authentication refresh-token into a query so I could push the JSON data directly into a worksheet.]  

Thanks to you all for taking the time to explain this to me….sadly it’s not a language I’m familiar so it’ll take a few days to work it all out….I’ll persevere though. Thanks again.

Are you just wanting the “Today’s balance” section from the home page?

Using the network tab of browser dev tools is the simplest way to reverse engineer the API.

Best I can see is that it uses a POST request to:

https://smartpaymapi.ovoenergy.com/bast/api/graphql

With the following body:

{
    "query": "\nfragment FuelFields on BillingFuel {\n  consumption {\n    rates {\n      rate {\n        pence\n      }\n      cost {\n        pounds\n      }\n      kwh\n      openingRead\n      openingReadType\n      intermediateReads {\n        date\n        read\n        readType\n      }\n      closingRead\n      closingReadType\n      startDate\n      endDate\n      friendlyLabel\n    }\n  }\n  standing {\n    netCharge {\n      pounds\n    }\n    rates {\n      rate {\n        pence\n      }\n      startDate\n      endDate\n      days\n    }\n  }\n}\n\nfragment PeriodFields on SelectedPeriod {\n  next\n  previous\n  data {\n    electricity {\n      ...FuelFields\n    }\n    gas {\n      ...FuelFields\n    }\n    upgrades {\n      description\n      grossCharge {\n        pounds\n      }\n      initialGrossCharge {\n        pounds\n      }\n      startDate\n      endDate\n      taxRate\n    }\n    transactions {\n      description\n      netCredit {\n        pounds\n      }\n      taxRate\n    }\n    payments {\n      date\n      description\n      credit {\n        pounds\n      }\n    }\n    start\n    openingBalance {\n      pounds\n    }\n    end\n    closingBalance {\n      pounds\n    }\n    totalCharge {\n      grossCharge {\n        pounds\n      }\n      netCharge {\n        pounds\n      }\n      vatCharge {\n        pounds\n      }\n    }\n    energyCharge {\n      pounds\n    }\n    isStatementAvailable\n  }\n}\n\nquery Period($id: String!, $index: Int!) {\n  billingSummary(id: $id) {\n    lastUpdated\n    billablePeriod(periodIndex: $index) {\n      ...PeriodFields\n    }\n  }\n}\nquery LatestPeriod($id: String!) {\n  billingSummary(id: $id) {\n    lastUpdated\n    latestPeriod {\n      ...PeriodFields\n    }\n  }\n}",
    "operationName": "LatestPeriod",
    "variables": {
        "id": "<account-number>"
    }
}

Remember to insert your account number. The balance should then be at data > billingSummary > latestPeriod > data > closingBalance > pounds. A negative number looks to indicate in debit.

It should be possible to tune the query in the body to only pull back the desired information, but I’m not familiar with graphql.

Just an additional question. I have tried that:

headers = {"Content-Type": "application/graphql"}

body = {
    "query": "\nfragment FuelFields on BillingFuel {\n  consumption {\n    rates {\n      rate {\n        pence\n      }\n      cost {\n        pounds\n      }\n      kwh\n      openingRead\n      openingReadType\n      intermediateReads {\n        date\n        read\n        readType\n      }\n      closingRead\n      closingReadType\n      startDate\n      endDate\n      friendlyLabel\n    }\n  }\n  standing {\n    netCharge {\n      pounds\n    }\n    rates {\n      rate {\n        pence\n      }\n      startDate\n      endDate\n      days\n    }\n  }\n}\n\nfragment PeriodFields on SelectedPeriod {\n  next\n  previous\n  data {\n    electricity {\n      ...FuelFields\n    }\n    gas {\n      ...FuelFields\n    }\n    upgrades {\n      description\n      grossCharge {\n        pounds\n      }\n      initialGrossCharge {\n        pounds\n      }\n      startDate\n      endDate\n      taxRate\n    }\n    transactions {\n      description\n      netCredit {\n        pounds\n      }\n      taxRate\n    }\n    payments {\n      date\n      description\n      credit {\n        pounds\n      }\n    }\n    start\n    openingBalance {\n      pounds\n    }\n    end\n    closingBalance {\n      pounds\n    }\n    totalCharge {\n      grossCharge {\n        pounds\n      }\n      netCharge {\n        pounds\n      }\n      vatCharge {\n        pounds\n      }\n    }\n    energyCharge {\n      pounds\n    }\n    isStatementAvailable\n  }\n}\n\nquery Period($id: String!, $index: Int!) {\n  billingSummary(id: $id) {\n    lastUpdated\n    billablePeriod(periodIndex: $index) {\n      ...PeriodFields\n    }\n  }\n}\nquery LatestPeriod($id: String!) {\n  billingSummary(id: $id) {\n    lastUpdated\n    latestPeriod {\n      ...PeriodFields\n    }\n  }\n}",
    "operationName": "LatestPeriod",
    "variables": {
        "id": accountIds
    }
}

response = requests.post(url, json={'query': body}, headers=headers,cookies=cookies) 

print(response.status_code)
print(response.json())

but I am getting an 401 with a message 

'OAuth plugin - No refresh_token present'

I have tried removing the headers and I am still getting the same error

I have done that, but I am getting that error. I must be missing something in the latest POST:

#POST REQUEST TO LOGIN/AUTHENTICATE
url = 'https://my.ovoenergy.com/api/v2/auth/login'
myobj = {
    "username": "ΧΧΧΧ@ΧΧΧΧ.com",
    "password": "ΧΧΧΧ",
    "rememberMe": True
}

x = requests.post(url, json = myobj)
#SAVE COOKIES
cookies = x.cookies

#GET ACCOUNT ID REQUEST
url = "https://smartpaym.ovoenergy.com/api/customer-and-account-ids"
y = requests.get(url, cookies=cookies)

#GET ACCOUNT ID BY MANIPULATING LISTS, JSON AND STRINGS
accountIds  = list(y.json().values())[0][0]

#POST REQUEST TO GET BALANCE
url = "https://smartpaymapi.ovoenergy.com/bast/api/graphql"
#headers = {"Content-Type": "application/graphql"}

body = {
##The same as above. I removed it avoid making the thread long
}

response = requests.post(url, json={'query': body}) 

third_query = "query LatestPeriod($id: String!) { \n  billingSummary(id: $id) { \n    latestPeriod { \n      data { \n        payments { \n          date \n          description \n          credit { \n            pounds \n          } \n        } \n        closingBalance { \n          pounds \n        } \n      } \n    } \n  } \n} \n"

query = {
    "query": third_query,
    "operationName": "LatestPeriod",
    "variables": {
        "id": accountIds
    }
}

response = requests.post(url,json=query)

I still do not understand what I am missing exactly. Is it in the headers? I have tried finding examples and playing around. I took the headers from the first POST (the login) and even made an update:

headers['Content-Type'] = "application/graphql"

I am not familiar with the authorisation and the examples online do not help

We love seeing the innovative ways our customers are using tech to help monitor and manage their energy usage. It’s inspiring us to think about ways to do energy differently. We know some customers have been using some of the application programming interface (APIs) behind our public facing services. While we’re OK with that, we do need to make you aware of a couple of things.

These APIs are designed to be used by OVO teams only, and aren't public facing. There are some downsides to using APIs that aren't for the public, and we wanted to let you know what these are. Behind the scenes, OVO uses APIs to share and update information between systems that power your bills and your online account. This is done in partnership with Kaluza, the tech company that’s part of the OVO family. They’ve built the billing platform designed to put our customers in the driving seat of their energy usage. 

These internal APIs are intended for use by Kaluza and its clients, who are energy retailers like OVO, rather than customers. Because of this, there’s no support for them being used anywhere else, which means they may be discontinued with no notice when we update our products and services. 

OVO Energy and Kaluza need to be able to monitor these APIs, and may block access if there's any problems in the future.

We know some customers may have put time and effort into developing solutions that use these API. So, now that you know the risks, we want to hear from you on how you’re using the APIs and the problems you’re solving with your DIY approach. 

Is there anything you’d like to see from OVO to help you monitor and manage your energy better? Leave a comment below to tell us.

https://shop.glowmarkt.com/products/display-and-cad-combined-for-smart-meter-customers

Works fine for getting me information into home assistant, and it's not likely to have the rug pulled from under you. 

I use the Home assistant api to get data for my OVO account but it's not real time. I’m aware of the Glowmarkt device but can't justify the cost to be honest.

I’ve pinged someone who creates one of the tools in question: https://github.com/timmo001/ovoenergy/issues/80

My experiments in this area have somewhat stalled. Partly due to pressure of family and work life but partly because I still don't have a smart meter. My one and only attempt to get one fitted some years ago resulted in the engineer saying he wouldn't touch the existing gas meter, that it needed someone else to change the mounting. I never heard back. Since then, so many of the people I know who have had one fitted have had nothing but problems, often going years (if ever) before they actually started working, I really don't want one at the moment. Also, since I work from home, I'm reluctant to have to power everything down to get new meters installed.

So currently, I grab my annual figures into a spreadsheet to monitor usage.

One thing that would be super cool would be if the Ovo app was better at showing a this-vs-last year comparison - at the moment, you have to keep switching back and forth between the years and the Y-axis changes making it hard to see visually.

Other than that, I would strongly urge Ovo to have a published API that customers can access using standard REST and appropriate open standards security. If for no other reason than it fits nicely with a “green” stance on helping people better manage and reduce power consumption.

However, the API should not only provide near real-time data from the smart meters but should also give access to the underlying customer data for those of us who don’t have smart meters and for those many people who do but they don’t work. That data would presumably just be monthly data but that is more than sufficient to be honest.

Personally, as I’m active in the Node-RED project, that is what I would use to grab my monthly stats, storing the data locally and showing on a dashboard using my own published UIBUILDER contribution to Node-RED. 😁

Node-RED is also accessible from Home Assistant but is easily run stand-alone and I use it for all my home automation as do many people. It is a low-code development environment and server based on Node.js. It has a very large and supportive user base and a very active community.

  That’s great, thanks very much 👍🏻

I must be missing a step. I’ve done all that (ignoring Windows Security warnings), selected a period (This month) and ended up with an apparently empty DB file (84kB) in ProgramData:
  

*edited by mod* 

What am I doing wrong?

The highlighted part of the screen shows what data has been read.