Hi Ovo,
I wondered whether the API that powers your live and historical usage page in the account menu is something you could look into opening up a bit so we can freely access our raw data and also perhaps it may stimulate some interesting community projects?
Best answer by g-de
Updated on 14/08/25 by Abby_OVO
Tim_OVO: “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.”
can you help me understand if the links above allow users to access raw data as if from an API?
I can certainly give it a go.
Firstly, big thanks to Timmo and other contributors for developing the library. All thanks go to them and links to buy them a coffee for their effort can be found on PyPi or GitHub:
https://pypi.org/project/ovoenergy/
https://github.com/timmo001/ovoenergy
I assume the way the library was developed this was to reverse engineer the My OVO website. That is, browse the website as normal and and monitor the traffic to see what OVO URLs and APIs it uses. Assuming this is the case, one of these URLs (get account IDs) already seems to be different but the library is still working for the moment. The APIs being used are not officially supported outside of the website, so first, a warning that any changes to the My OVO website may break the library.
For anyone using Python, you should be able to include the ovoenergy library and look at https://github.com/timmo001/ovoenergy/blob/master/ovoenergy/cli.py for how to use it.
For replicating this in other languages, the process seems to be as follows:
{
"username": "...",
"password": "...",
"rememberMe": true
}From the response, save the cookies to use in all future requests.
You can also get monthly or half-hourly usage using the following URLs similar to step 3:
As mentioned above, if this is wanted for Home Assistant, the integration was added in version 0.114 (https://www.home-assistant.io/integrations/ovo_energy/).
Unfortunately the data only goes up to the end of the previous day as OVO no longer provide real-time data:
+2Please confirm
PS:
In order to save the output in the same folder as the exe I had to specify .\output.csv as the file name
You can put them in there to save typing them all the time! Thats all. Then you can omit those params from command line.
Ought to be in the readme (as a programmer I guessed that might be the case)
If I add my username and password into the settings json file I get
OvoData.exe -f 01/01/2020 -t 04/02/2020 -o .\OvoData.csv
Unable to login - 401 - Unauthorized
at OvoData.OvoLiveRepository.OvoConnect.GetLoginCookieAsync(String userName, String password)
at OvoData.OvoOrchestrator.ExportData()
at OvoData.Program.EntryPoint.Run()
+6Please confirm
Hmm, i would think so I am afraid but i will see if i can make a docker version for mac or linux users.
+6If I add my username and password into the settings json file I get
OvoData.exe -f 01/01/2020 -t 04/02/2020 -o .\OvoData.csv
Unable to login - 401 - Unauthorized
at OvoData.OvoLiveRepository.OvoConnect.GetLoginCookieAsync(String userName, String password)
at OvoData.OvoOrchestrator.ExportData()
at OvoData.Program.EntryPoint.Run()
Oh! Erm, please just use commandline then no idea why that didnt work! (You kept the "" right?)
+6Yes, if the api changes it could stop, but also the apis are soft coded in the config file so if a trivial change the config will just need updating. The risk of any 3rd party integration exists if any 1st party changes an apinin any situation.
If ovo want to see the code , then i am happy to discuss.
+2i will see if i can make a docker version for mac or linux users.
Linux would be great :)
Raspberry-Pi or Arduino would be better still because we can then make our own IHDs 
Btw, I can confirm there is no risk of insecure as you will see from the command line the details are on your machine and provided to directly access ovo, the exe has been made by best practice .net core code and is a standalone on pc only exe.
Is the program open or closed source?
If I add my username and password into the settings json file I get
OvoData.exe -f 01/01/2020 -t 04/02/2020 -o .\OvoData.csv
Unable to login - 401 - Unauthorized
at OvoData.OvoLiveRepository.OvoConnect.GetLoginCookieAsync(String userName, String password)
at OvoData.OvoOrchestrator.ExportData()
at OvoData.Program.EntryPoint.Run()
Oh! Erm, please just use commandline then no idea why that didnt work! (You kept the "" right?)
Yep, I kept the quotes to make sure it’s still valid json string.
Yes, if the api changes it could stop, but also the apis are soft coded in the config file so if a trivial change the config will just need updating. The risk of any 3rd party integration exists if any 1st party changes an apinin any situation.
If ovo want to see the code , then i am happy to discuss.
Warning: This only protects the user if the API end-point changes, not when the format of data it fetches changes.
Hi All,
I have just written a PowerShell script to fetch all of my readings from January 2017 to present-day a month at a time.
You can find it on GitHub at
https://github.com/MikeWilliams-UK/Bulk-Fetch-Ovo-Readings
Have fun
Here is it: The API exe I promised that takes all that HH data and nicely formats it into a consumable Sheet
https://drive.google.com/drive/folders/1A7XRov0579O53T8OsIGe3wXCk09jul0F?usp=sharing
Download all the files, and read the Readme! (oh, and Enjoy) - now I can start work on ther TOU comparison tool!!
If anyone is willing to send me their export please do! - It will help me build the tooling.
John (at) QuinlanServices (dot) Com
Examining the downloaded csv file
Not sure if these are your columns, but the output could do with tidying up.
As a programmer I can help with this.
+6Btw, I can confirm there is no risk of insecure as you will see from the command line the details are on your machine and provided to directly access ovo, the exe has been made by best practice .net core code and is a standalone on pc only exe.
Is the program open or closed source?
At the moment I am discussing if I should open source it or if OVO themselves may be interested to make it or a basis of it integrated as a supported offering.
Btw, I can confirm there is no risk of insecure as you will see from the command line the details are on your machine and provided to directly access ovo, the exe has been made by best practice .net core code and is a standalone on pc only exe.
Is the program open or closed source?
At the moment I am discussing if I should open source it or if OVO themselves may be interested to make it or a basis of it integrated as a supported offering.
Would be good if it were made open source, then the community could help to fix any issues.
+2There’s another issue to consider if OVO were to take this on. I believe that their new Billing System is being developed such that it can be licensed to 3rd parties. Such an arrangement means that they would need to secure some rights over any externally-sourced code within the suite and be able to provide rapid support if an element of that code were to fail or require upgrading.
That’s a legal minefield.
And let’s remember that it was the failure of a 3rd party software provider to resolve issues with parts of their billing system which caused OVO to embark on creating their own in the first place. It didn’t help that Ofgem clobbered them with a hefty fine for the failed usage-estimation provisions in that software.
You will understand that there would be a significant level of reluctance for OVO to become embroiled in such a scenario again.
Sorry for another spamming comment but I’m keen to hear if others have checked out this work done by
+6On a side note, a v2 with fixed year field coming next week.
Sorry for another spamming comment but I’m keen to hear if others have checked out this work done by
In the same boat without an account now,
So not unless it’s open-sourced, especially when they managed to make it almost 100mb in size. I’d say no to running that
Gave up when I saw the file extension, was hoping for something written that I could run on my Pi. I tried to decompile it using Visual Studio but didn’t get far.
Gave up when I saw the file extension, was hoping for something written that I could run on my Pi. I tried to decompile it using Visual Studio but didn’t get far.
Looks like C++ I’m guessing it’s using a large library for the http requests and that’s taking up the size, but haven’t had too deep a look myself
Not sure who to ask this question of. Possibly
I have a smart meter on the V2G trial. I have the Kaluza phone app and the OVO Computer app. If I want to see my half hourly imports, exports to The Grid and Exports to the house I simply go to the Kaluza phone app and click on the download arrow in the top right corner of the screen and I can download the complete month’s data in spreadsheet form, ready to go on my Apple computer.
If I want to do the same with my OVO account I can get the data on a daily basis showing ½ hourly info but there is no way (that I can see) how to download the info…..other then highlight the numbers...but then it’s not compatible with Apple’s “Numbers” App and I have some copying and pasting to do...for every day of the month.
If Kaluza have the ability to download the data easily, do OVO have a similar method that I've missed...and if not, are there any plans to do so? At present the data for Kaluza is brilliant but OVO is a struggle.
Can you also tell me, The National Grid record data in GMT throughout the year, even when it’s BST but some sites record data an hour later than the clock time...explained that for Solar Data, Mid Day isn’t always 12.00 noon, sometimes before and sometimes after so it’s recorded so that 1.00pm is actually 12.00 noon. Hence to avoid the extra hour in Winter and lesser hour in Spring the time is always recorded GMT. Is the time data as recorded by OVO the same time as Kaluza and is this time GMT?
Hi
Great second question, add your first question is a popular one. The answer is currently that there isn’t a way to download online account usage.
The second question, I know that smart meters use a time switch that DOESN’T change in BST vs GMT. Which means peak / off peak usage shifts forward an hour. However I don’t know how this impacts the online account. My assumption is that the online account uses a system to correctly shift usage blocks in terms of local time.
Thanks for that
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
OVO Energy Ltd, registered office 1 Rivergate Temple Quay Bristol, BS1 6ED, company no. 06890795 registered in England and Wales.
OVO (S) Gas Limited is registered in England and Wales (Company No. 02716495) at 1 Rivergate, Temple Quay, Bristol, BS1 6ED.
OVO (S) Gas Limited is part of OVO Group Ltd
